Upload File without creating a new generation
I wish to create an Action for the Document ItemType that 1. Prompts the user to select a file, 2. Uploads the file, and 3. Does not create a new generation of the Document Item. Use Case: A Document, for example at Rev C, are reviewed via the out-of-the-box (OOTB) Document Change Object. Prior to the Release step, a PDF file is generated and submitted to the customer. The workflow is then completed, setting the state of the Document as Released. The PDF is sent to the customer for approval. And a new revision, Rev D, of the Document is started using subsequent DCO. Not a problem. The customer returns a wet-ink or digital signed PDF file of the Rev C of the Document. This version of the PDF is to be included in the the latest generation of Rev C, which most probably will have been updated by Rev D and subsequent generations. It is not appropriate to add the signed PDF to Rev D or later iteration. This process is possible using AML, by 1. Determine the ID of the latest generation of Rev C of the document. 2. Using admin, drag and drop the file into the file vault. 3. Get the ID of the file, after it has been uploaded, and 4. Using AML <AML> <Item type='Document File' action='add'> <source_id>id of the document at the correct generation</source_id> <related_id>id of the uploaded file </related_id> </Item> </AML> Can the above sequence be done using an Action, a Form with a File Item field or some other method?
Instruction: Changing the Header Logo in Aras Innovator V12
Hello everyone, Here is a short instruction on how to change the client header logo when logged in into Aras V12. Whereas V11 used a simple .svg file inside the code tree, in V12 we need to dive a little deeper: Open the TOC and go to Administration > Configuration > Client Presentation Perform a search and open the single record that you find named 'JavaScript' On the 'JavaScript' item, click on the 'Global' item / URL On the 'Global' item, open the 'Command Bar Section' relationship and expand the 'Name' column Scroll down until you find an item with the name 'com.aras.innovator.cui_default.mwh_header' and open it On the 'com.aras.innovator.cui_default.mwh_header' item, open the 'Command Bar Section' relationship and expand the 'Name' column Find the item with the name 'com.aras.innovator.cui_default.mwh_header_logo' and open it Click 'Edit' and attach your logo file to the property that has the 'Image' label Note: using .svg files is recommended by Aras because it scales without stretching and your logo will not get blurry or pixelated (.svg is a vector format). I hope this helps. All the best from Almelo. DaanItem.apply overwriting action, has it always done this?
After upgrading from version 12 to 31, we started getting an error when saving a certain custom datastructure, developed for us by Minerva back in the day: Failed to execute 'serializeToString' on 'XMLSerializer': parameter 1 is not of type 'Node'. From what I can tell, this happens because Minerva's old code calls an action directly on the document.thisItem object var output = document.thisItem.apply("VE_GetCopyTreeGridHeader"); which "pollutes" document.thisItem with that action. When later hitting save, it calls this function instead of doing whatever it ordinarily would (probably a get action), resulting in the error. I observe that if I change the action to "get", it gets rid of the error message and saves any changes in the object itself, but not in a related items treegrid associated with it. If I change the Iaction to "update", it saves everything correctly the way it used to do in version 12. I see that the docs on item apply says that it overwrites the action, but if it always did that, how did this code ever work? (By the way, that .apply() overwrites the action is an error-prone side effect which I can't see any good reason for)
Making changes to typescript files in the tree
I tried to apply a trick from a previous post: How to open StartItem directly without the helper window - Development - Aras Community - Aras Community However, that file is now a typescript file in my tree. I guess that means I need to transpile it to javascript/do whatever else you at Aras do in your frontend build process, in order for it to end up in the right place? What is the recommended way to do this?
