I would like to know how to achieve below requirements using configuration in Agile but not PX,kindly help.
1.Change has a list ,list has the value consist of yes/no, if you select ‘Yes’ means one workflow should be set to change , ‘no’ means another workflow should be set, how to configure it.
2.In attachments tab, ‘attachment type’ attribute should be visible to one group and another group should not see, how to configure it.
3.Item has some attribute called X, when you add the item to change, the same attribute should be on the change’s affected item table, but we should not create a new attribute on change’s affected item table, instead we need to link the X attribute from item to the change, how to configure it.
I can try to answer on #2 and #3
For #2, yes – Checkout documentation on “Enforce field level read” privilege. You could create a role with this privilege, you can then create a “Read” privilege with all the fields they need. Grant that role to the group
Regd #3, yes – that is also possible. Check out the Administration guide for “Read-Through Fields Made Consistent in Items and Changes” section. There is one limitation. User defined fields cannot be linked
Hope this helps
The only thing I can think of for #1, is using the “Workflow Matching Criteria” for each workflow. Basically create a criteria for “Change Orders with ATTRIBUTEXX in “yes” and set this for one workflow. Then create another for “Change Orders with ATTRIBUTEXX in “No”” and apply it to the other workflow. This would mean only the workflows matching the criteria conditions would be available to chose from the “Workflow” drop down on the cover page.
I don’t think your first requirement could be possible without PX. You can check attribute value using workflow criteria and allow to set of values but you can’t set it without px. To set value in attribute you need a external event or Java PX/Event.