Question
EY
BR
Last activity: 30 Jan 2017 18:56 EST
Generate Specification Document with many version of ruleset
Hi All!
I made an update on an specification that was created in a ruleset that has many Patch Versions, and the changes were not in the last one.
I´m trying to generate the Specification Document using the Designer Studio Document tool, but when I filter the ruleset, it´s just display the last version of that ruleset.
For instance, the ruleset has that versions:
01-01-01
01-01-02
01-01-03
01-01-04
01-01-05
And I made changes in the ruleset 01-01-02, but only 01-01-05 is displayed in the filter.
How could I generate the Specification Document of a different release/patch version of ruleset?
Pegasystems Inc.
US
Hi - 2 quick questions to help clarify and provide a better answer.
1) What version of Pega (i.e. 7.1?)
2) In your scenario, does the same specification exist in one or more of the higher ruleset versions (but it's not the one you want), or does it only exist in 01-01-02?
01-01-02 -- version of spec I want
01-01-05 -- future version of spec, has updates that are not in scope yet, don't want to print this one
EY
BR
Hi David!
About your questions:
1) The version is 7.1.8
2) The same specification exists in others ruleset versions, but the one I wanna generate the spec doc is 01-01-02.
Thanks for your help.
Pegasystems Inc.
US
Hi - In this scenario, I think your best bet is to work with an application version and access group that is limited to patch version 01-01-02 and then run the documentation wizard while using that access group. Note: If this type of application versioning and access group versioning is already being done, you can leverage it. If this doesn't exist, you'll want to work with you LSA or another resource experienced with the Pega security components to get help with the setup.
Below is a quick explanation of the parts and pieces...
Application 01.01.02 --> this application is setup to have ruleset version limited to 01.01.02
Access Group 01.01.02 --> has access to "Application 01.01.02"
Your Operator ID setup with "Access Group 01.01.02"
This setup should limit the available specification versions to 01-01-02 when you run the documentation wizard or if you use the gear icon to just generate the document for the 1 specific spec from the spec overview page. Note that I tested this with Pega 7.1.9 personal edition as I had that version handy. When I tested it, the table shown in the documentation wizard still said it was spec version 01.01.05 (higher version) but when I actually generated the document I verified that it was the older version of the spec as desired.
Hi - In this scenario, I think your best bet is to work with an application version and access group that is limited to patch version 01-01-02 and then run the documentation wizard while using that access group. Note: If this type of application versioning and access group versioning is already being done, you can leverage it. If this doesn't exist, you'll want to work with you LSA or another resource experienced with the Pega security components to get help with the setup.
Below is a quick explanation of the parts and pieces...
Application 01.01.02 --> this application is setup to have ruleset version limited to 01.01.02
Access Group 01.01.02 --> has access to "Application 01.01.02"
Your Operator ID setup with "Access Group 01.01.02"
This setup should limit the available specification versions to 01-01-02 when you run the documentation wizard or if you use the gear icon to just generate the document for the 1 specific spec from the spec overview page. Note that I tested this with Pega 7.1.9 personal edition as I had that version handy. When I tested it, the table shown in the documentation wizard still said it was spec version 01.01.05 (higher version) but when I actually generated the document I verified that it was the older version of the spec as desired.
Good luck, hope this helps. It would be great if it was easier. One thing we have done on projects in the past is include the target iteration / sprint in the name and ID of the spec, that ends up providing a unique name / id as well.