Introduction
After upgrading Service Desk to 14.1.03 (Hampi) customers have been realizing that properties added to areas have activity associations when changed during a ticket editing. It is an enhancement compared to earlier versions and now, customers are able to figure out if there were modifications in properties added to areas. Before, only ticket fields had activity associations. There was no way to figure out if users changed properties. Now it is possible also for properties added to areas!
See below a property being added to an area:
Question
During a upgrading project, a customer asked: Is there a way to disable it? I mean, is there a way to keep the same behavior for activity associations compared to earlier versions? I know it is a enhancement, but on the other hand, I do not want to have activity associations for area properties editing.
See the property being edited:
Now see the activity log:
Environment:
Service Desk 14.1.03 (Hampi)
Answer:
Yes, there is way!
It is a pretty simple spel code you can put on NX_ROOT\site\mods\majic.
See the file my_spel.spl:
Now see the code:
cr_prp::insertActivityForCatProps(...)
{
}
Additional Information:
Even tough it is a pretty simple spel code, it is a kind of customization. Useful in order to attend a project requirement when customers want to see a feature with the same behavior they have seen in earlier versions. CA Support recommends you follow the best practices for making changes in spel code, as well the best practices for testing it in test environments before putting it in production.
Do not do it in production before testing!