I know that the trigger manager is listed in the System Admin manual. But is there any other place that lists all of the triggers, and explains what each one does, and how it works? I have gotten the hang of using a few of them. But a manual explain all of their specific functions, and how they could be used would be great.
More information about Triggers
Deborah_Sherwood
(Deborah Sherwood)
#2
[quote]I know that the trigger manager is listed in the System Admin manual. But is there any other place that lists all of the triggers, and explains what each one does, and how it works? I have gotten the hang of using a few of them. But a manual explain all of their specific functions, and how they could be used would be great.
[right][post=“14745”]<{POST_SNAPBACK}>[/post][/right][/quote]
I am currently working on the new version of the CMS manual - the new version of the System Administrator manual is next on my list. This will contain all of the new triggers for v3.12.
I am also thinking about making a new Triggers manual for v3.14 that will explain each of the events, conditions and actions. It will also include examples on how to set up some Triggers like automatic content reveiw dates and automatic password expiry.
What do people think about having a Triggers manual? Do you think its worth developing it?
kjb
(Keith Brown)
#3
[quote]I am currently working on the new version of the CMS manual - the new version of the System Administrator manual is next on my list. This will contain all of the new triggers for v3.12.
I am also thinking about making a new Triggers manual for v3.14 that will explain each of the events, conditions and actions. It will also include examples on how to set up some Triggers like automatic content reveiw dates and automatic password expiry.
What do people think about having a Triggers manual? Do you think its worth developing it?
[right][post=“14756”]<{POST_SNAPBACK}>[/post][/right][/quote]
Well I think that a ‘Common Examples’ manual accross the entire app. would be interesting (although that might cut into the training income?). It’s sometimes quite difficult to make the jump from ‘this is what it does’ to ‘this is how you can use it’.
As an aside I’m a bit surprised that for such a good product there isn’t more of a community writing this stuff outside yourselves. Certainly thinking about writing a couple ‘how tos’ when I have time 
K
Andrei_Railean
(Andrei Railean)
#5
The only list of Triggers that may exist in you system is the one that you create. You should play with triggers - create a dummy (disabled) trigger to see what options (building blocks) are available to you.
Each trigger you define consists of a combination of
- events (starts the trigger)
- conditions (that need to be satisfied for the actions to run)
- actions (all the good stuff is done here)
No manual will be able to provide you with a complete list of all possible combinations and usefulness of any particular combination.
Each action/condition is supposed to be self-explanatory. If something is not clear, ask questions on these forums.
As a concrete example. When I setup a testing system and want to save a few mouse clicks I create the following trigger:
event: Asset Created
conditions: (none)
actions:
- Make Live (changes the status of the asset to Live - default is under construction)
- Give "Read" permission to user "Public" (by default the creator or the admins can see it).
This makes every asset readable to all from the moment of creation.
You could also create links, send email, set attributes and perform other business-specific logic.
Be aware that executing one trigger may trigger others.
I.e. if in the system that has an example above (Live & Public) there is a trigger like this:
event: Status Changed
condition: Current status is Live
action: Change status to Under Construction
This trigger will execute and negate some of the effect of the first trigger. It's possible to create insane situations like: if link created -> create asset, if asset created -> create link, so if the conditions are wrong you will end up in an infinite loop.
Hope this helps while the manual is being developed.
gsherwood
(Greg Sherwood)
#6
A triggers manual would likely contain the most common trigger setups that are used to provide functionality that Matrix does not include out of the box. For example, force users to change their password after x months.
I don't think anyone is suggesting that a manual could list all possible combinations, or even just all useful combinations. Just the most common should do, and enough for the reader to get the hang of creating triggers.
julz
(Tavernerj)
#7
[quote]I am currently working on the new version of the CMS manual - the new version of the System Administrator manual is next on my list. This will contain all of the new triggers for v3.12.
I am also thinking about making a new Triggers manual for v3.14 that will explain each of the events, conditions and actions. It will also include examples on how to set up some Triggers like automatic content reveiw dates and automatic password expiry.
What do people think about having a Triggers manual? Do you think its worth developing it?[/quote]
Yes, yes, & yes how's this going? I note that in the Sys Admin manual 3.16 there's little reference to Triggers, so anything would be helpful 
.
kylebuttress
(K Buttress)
#9
[quote]Well I think that a 'Common Examples' manual accross the entire app. would be interesting (although that might cut into the training income?). It's sometimes quite difficult to make the jump from 'this is what it does' to 'this is how you can use it'.
As an aside I'm a bit surprised that for such a good product there isn't more of a community writing this stuff outside yourselves. Certainly thinking about writing a couple 'how tos' when I have time
K[/quote]
I like the idea of some howto's i'd be interested adding some and reading others.
julz
(Tavernerj)
#10
Thanks Deb, it's very good. If I could make one suggestion, is it would be nice to have an example that you stepped through as you went through the manual.
Other wise I'm a happy camper :D