When using issueDelta bean in trigger and performing any edit operation it skips or surpass all editability rule, constraints, visibility restrictions, if item is in end state etc. and perform the edit operation successfully.
But when we do edit operation using API commands then we have to take care about everything otherwise edit operation might not be successful.
- Editability Rule
- Constraints
- Mandatory fields are unspecified and your group is not authorized to modify those fields.
- Project/type visibility restrictions
- Not in end state.
There should be one permission something like (Anonymous User or Anonymous Login) which we (Administrator) can give to any specific user (IntegrityAdmin mostly) or entire Administrator group based on organizational need. But once given then during API edit operation as well (if perform with the user having permission) it will skip or surpass everything and works like delta.
(PS:Sometimes we have conditions we can't go with delta and have to perform edit operation using API's )
Looking forward to hear from you, learn any technical dependency or workaround etc.
Vielen Dank / Many Thanks,
K. Jain
