Forum Discussion

Former_Member's avatar
Former_Member
Accelerator III
9 years ago

Why does Aras doesn’t allow me to create 2 revisions without releasing prev

I am evaluating Aras for intermediate storage of PLM data during data exchange. As part of this use case I want to create multiple revisions of the Parts even without releasing the previous one. I explored Aras documentation and tried various configuration changes but I am not able to achieve this behaviour. In this regard I have following questions: 1) Why does Aras enforce me to release previous Revision(A) before I can create new Revision (B)? Why cant I have multiple revisions as working revisions? 2) I understand this is OOTB behaviour, is there a way to configure or customize this behavior to suit my needs? Thanks and Regards, Pravin

1 Reply

  • eli_donahue's avatar
    eli_donahue
    Community Manager
    9 years ago
    Hi Pravin,
    1) Why does Aras enforce me to release previous Revision(A) before I can create new Revision (B)? Why cant I have multiple revisions as working revisions?
    This is the standard versioning logic that Aras uses for versionable ItemTypes, and an important part of the Product Engineering change items. If you'd like to know more about the PE application and versioning in Aras, the Aras Community team may have more information available or you could check out the content on our demo page.
    2) I understand this is OOTB behaviour, is there a way to configure or customize this behavior to suit my needs?
    Yes, it is possible to implement custom versioning logic using properties and ItemType server events. For example, you could create properties "my_rev" and "my_version" to track the revision and version of each item. You could then use onBeforeAdd/onBeforeUpdate events or a custom ItemType action to set the custom revision/version properties according to your specific business logic.