ESI Failure since user did not have create rights for Transaction

[avillanueva]

Side effect of flipping who creates out Change Notice objects. We had previous automated creation so wcadmin was the creator. We finally flipped back to more OOTB where uses can create (I do not use Change Admin roles). When the ESI workflow kicked off, it failed since the creator of the CN whom it uses in ESI did not have rights to create an ESI Transaction. Simple to fix by granting rights at the Org level in Systems domain like it suggested but strange that I had to do this.

2022-12-21 11:38:33,399 ERROR [SessionThread-825] wt.access.evaluation.report  - "XXXXXXX" does not have Create permission for "Enterprise Systems Transaction - " in Administrative Domain "Site, Organization - MYORG /System".
2022-12-21 11:38:33,404 ERROR [SessionThread-825] com.ptc.windchill.esi.txn.ESITransactionUtility  - Error while creating ESITransaction object.
(wt.access.accessResource/19) wt.access.NotAuthorizedException: ATTENTION:  Secured Action. You do not have the necessary authorization for this operation. Contact your administrator if you believe you have received this message in error.

I would have thought it would have been handled by system.

[avillanueva · Accepted solution]

Linking some other articles and posts I found on  this topic:

https://community.ptc.com/t5/Windchill/If-the-CN-Initiator-removed-from-the-License-groups-Termination/m-p/695357#M63061%3Fsource=search

https://community.ptc.com/t5/Windchill/What-is-the-purpose-of-the-ESI-Author-and-ESI-Administrator/m-p/330101#M38761

https://support.ptc.com/help/wnc/r12.1.1.0/en/index.html#page/Windchill_Help_Center/esi_admin/ESIAddUsersToGroupMapRoles.html#

One thing does have me a bit concerned is that if the CN initiator leaves the company before the CN is completed, will the ESI workflow always fail since the initiator does not exist? I will have to test this one out.