cancel
Showing results for 
Search instead for 
Did you mean: 
Billy.Kidney
Staff
Staff
Status: Delivered

When a process or business object's name is changed all references to that process or business object are lost.

This great affect reusability and results in artifacts with improper names to retain references.

Proposed Solution:
Artifacts have a NAME (static for DB), LABEL (shown in GUI for ease), and DESCRIPTION. This will allow artifacts to have their LABEL updated easily without breaking any references to that artifact.

13 Comments
tomsadler
Staff
Staff

Hi @Billy.Kidney ,

Thanks for your suggestion. What you describe is actually the behaviour that we have today in the WorkHQ Digital Workers offering (previously 'Next Gen RPA'). We manage object or process linkage via an AssetID, rather than Asset Name, meaning that you can change the name without breaking the link to the embedded asset.

So, in short, this feature is 'delivered' in WorkHQ Digital Workers. 

Thanks,

Tom

Status changed to: Delivered
tomsadler
Staff
Staff
 
Status changed to: Delivered
Otto_Mation
Level 2
This idea has been updated by the SS&C Blue Prism Product Management Team