Share all details about your problem, including any error messages you may have received.
I have a requirement to rename the application in the Production environment. In past I have used the IIQ console command rename to achieve this thing. However, from the SailPoint support team I got to know that this is not a right way to rename the application name .
We have scenarios in which we have to rename the applications to match the name exact as is in the application inventory database. Hence, looking for the best approach to rename the applications.
In the objects where the application name is referred instead of the application id (e.g. taskdefinition, AuditEvent etc)
All the rules/scripts where we reference the application names.
Note: In case you tokenized the application name, and changing the name in the token may create a new set of objects for the application instead of renaming the existing one (this is my observation from the past).
Hi @ Zeel Sinojia,
The only approach available is renaming the application via the UI. However, before renaming, all references to the application such as in rules, workflows, and other configurations must be updated accordingly. If the application name is not referenced anywhere, it can be renamed directly.
The worst problems we’ve had were with IdentityArchive objects (in the spt_identity_archive table).
If there are references to the old application name in there, then you will get null pointer exceptions seemingly at random.
There isn’t a good way to clean up the stale references.
Here is an sql query you can use to find stale references from the spt_identity_archive table:
select ia.name, ar.id, ar.name
from identityiq.spt_identity_archive ia
cross join xmltable('//Link/ApplicationRef/Reference'
passing sys.XMLType(substr(ia.archive,99))
columns
id varchar2(32) path '@id',
name varchar2(128) path '@name') ar
left join identityiq.spt_application a on a.id = ar.id
where a.id is null;
What to do when you’ve found stale references? The easy thing to do is delete the problem rows from the database, but you may miss some attribute changes that should trigger workflows