Creating new items via aras.uiShowItemEx doesn´t add LifeCycle data especially for versioned ItemTypes. How to fix?
Hi community, I have a couple of ItemTypes with a custom LifeCycle. Sometimes when users promote an item to change the "state", the Form will not be updated and will not show the updated data. In this case users always had to click the refresh button to see the updated state. So the basic situation is something like this: I discovered that the Form update mainly fails when the item was created via a custom client Method. AND: In addition it only fails if the target ItemType is versionable. Here are some simple steps to reproduce the scenario. Let´s assume we have following code that we can directly execute from a client Method: [embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:19604769-ada7-4f06-92ad-60eb8ae9dadd:type=text&text=const%20newItem%20%3D%20aras.newItem%28%22Manufacturer%22%2C%22add%22%29%3B%0Aaras.uiShowItemEx%28newItem%2C%20%22tab%20view%22%29%3B] The code will add a new item and opens it in a new tab. User than can save the item and promote it to another state. - If the ItemType is something like Manufacturer, Form update will work after item promotion. - If the ItemType is versionable like Part or Document the Form update will NOT work. I checked the context item that is used for promotion. I noticed that for versionable items the LifeCycle data is not included in the context item when we come from a custom Method. When using promote, the context item should contain information about the used LifeCycle like this: But the life cycle State information is missing when promoting a versionable item that was created by Method I wonder if this is a bug in innovator or if I forgot something in my Method code. The update error does not occur for of items that were created via the regular "New item" button. I assume the missing LifeCycle data causes the problems with the Form update. Does anyone know how to improve this one? Thanks for any hint! Angela
Bringing items in through AML package as 'Released'
Hello all, I am working on importing custom itemtypes to load via AML package as part of new builds. Due to how a customized contextual window displays these items, I need the items to be in a 'Released' state when they are brought in. (The window will only display 'Released' items). However, I am having difficulties getting the items to be in a 'Released state' 1. I've tried adding a <state>Released</state> to each item being brought in 2. I've tried adding a postAMLpackagedeployment script that adds a <state>Released</state> to each item The catch is, I need the items to abide by its lifecycle/workflow normally when edited and the state returns to 'New'. Is this possible?
How to get comment from LifeCycle promotion in Pre server method?
Hi all, I want to obtain user comment from Lifecycle promotion when user promotes item to next state. Idea is that Pre method on LifeCycle captures comment and if comment is empty, method prevents promotion. I would appriciate it if someone knows the answer. Thank you. RokLifeCycle Get History Comment -> Can we retrieve the user input on runtime?
Hi Community, I have a short question regarding the 'Prompt History Comment' feature that we can use in LIfeCycles. When we choose "Get Comment = 1" for a LifeCycle Transition, the end user will be asked with a dialog to add some notes why the lifecycle was changed. This is for e.g. useful, when a LifeCycle was Cancelled and user can explain why they cancelled it. The comment than appears in the History of the item. When my LifeCycle is Cancelled, affected users will get informed by email. It would be helpful if the history comment would be included in the mails. Is it possible to pass the user input to an Email Message? Of course I could make a query for the new history entry, but I want to avoid query on the History, cause it´s quite performance consuming. Hope anyone has an idea! Thanks for any help! Angela
PSW lifecycle state promotions
Hello, How is the lifecycle promotions for the part submission warrant set up out of the box? I can see that there's a "PPAP Lifecycle" r the PSW. Is it connected to any of the OOTB change management items or are you meant to manually promote the PSW? Are you meant to make your own workflow map for the PSW? It doesn't seem like I can promote it manually either. I'm using aras 11 sp12. Best Regards Rick
Relation and versioning
Hi, I have an ItemType STUDY with a property (type=Item) pointing on an ItemType CONTEXT. The CONTEXT is versionable and has a simple lifecycle WIP => REL. I would like that: When the relation is created, the STUDY is pointing on the last version/generation of the CONTEXT When the CONTEXT is modified (same version), the STUDY is pointing on the last version/generation of the CONTEXT When the CONTEXT is released (LF set to REL), then all STUDIES are now fixed on this version/generation To do that: I set the "Item behavior" of the property to "Float" On the LifeCycle, I set the ""Item behavior" of the state "REL" to "Fixed" But, the point (3) of my expectations doesn't work, if I create a new version, the study is pointing now of this new version. What should I do?
