Hello @Dima_M,
thank you a lot for your example. It is really nice. I would like to ask you for some advice regarding my use case. Let's say that we have some highly sensitive rules. Nobody should be able to add rule above them to break their drop meaning. I was thinking tu use smart task and before publish trigger for checking of this concept.
Concept of checking of modified/deleted/added objects in rule base is really nice.
{
- "operations":{
- "modified-objects":[],
- "deleted-objects":[],
- "added-objects":[]
}, - "session":{}
}
We would totally be able to check if rules were edited. But during the testing I tried to move "permit any" rule above those "highly sensitive rules". I was checking parameters of publish event, and when I changed rule order and published information, the only info in JSONs was about session itself, no info about rule number change. So I have no evidence about changing of order of rules while publishing new rule base and running some smart task on it. Is this information somewhere hidden? How can I get to this information during "before publish" event?
Thank you a lot for your reply.
{
- "session":{
- "session-uid":"104cd16c-dcbc-4749-9758-89f04d8d7c30",
- "session-name":"admin@02.04.2020",
- "user-name":"admin",
- "application":"SmartConsole",
- "domain-info":{
- "uid":"41e821a0-3720-11e3-aa6e-0800200c9fde",
- "name":"SMC User",
- "domain-type":"Domain"
}
}
}