Generate tasks based on custom attributes
It would be useful if adding a custom attribute to an event triggered workflow, especially if the workflow could be based on the value of the custom attribute. (e.g. different notifications depending on whether a Boolean attribute is Yes or No)
Comments: 5
-
10 Jul, '20
Walt M (CollegeNET) AdminThere is a current path to this. Using a 25Live Pro Event Form Rule to automatically add a Resource based on a custom attribute value will generate the appropriate Assignment Policy for said Resource.
Coming in the current Pro Sprint (7/16/20 expected release) is the ability to add an Event Requirement based on a Pro Event Form Rule. Adding the Requirement will trigger any related Notification Policy on the Resource.
We have also talked about the creation of a To Do task based on a rule... -
10 Jul, '20
Walt M (CollegeNET) AdminEvent Save Email Scenarios can also be triggered by using Custom attribute values. The email templates can also include the custom attribute information in the body. These can be used to enable communication based workflow (outside of tasks based workflow).
These can be set up using code view in the Event Save Email Scenarios and Templates - contact me if you need help setting these up! -
23 Sep, '20
iyanHello Walt and College net,
We would love this with todo tasks with the variables related to the event start date or creation date. such as adding a custom attribute would create a todo that is do 60 days before the event start date or conversely 30 days after the event created date. -
23 Oct, '20
Mike C (CollegeNET) AdminThis has been completed with Event Rules which can add both Resources and Requirements which can produce workflow.
-
02 Jun, '23
Pamela MasonI would say this is not Done. These is a workaround for this but I still want the actual request. I want to be able to create ToDo Tasks based on the value of Custom Attributes. I don't want to add a Resource or a Requirements. This adds other things that clutter up events and cause issues or confusion for people when they try and edit their events. For Example: If I used a Resource I would have to make it not visible/not requestable so people do not remove it when it has not even been taken care. There is also no need for the Resource to be on there. This is especially problematic for complex events that already have all kinds of Resources on the event.
Using Requirements is just creating duplicate work and having more things that need to be maintained. This also does not work with tiered workflow. I don't want these tasks to not appear until the very end.