Status Processes
SeedCodeComplete3.StatusProcesses History
Hide minor edits - Show changes to output
Changed lines 13-25 from:
Both the contact and project status fields have OnObjectModify script triggers tied to them. In Contacts this calls the script "Contact Status Changed" and in projects the trigger calls "Project Status Changed"
This project script "Project
-> The script can email project staff and/or project contacts about the status change. A switch to enable this is found in the script after
-> Finally, the script asks if you'd like to apply any Process Templates tied to the new status.
The contacts version of the script is much simpler and just looks for Process Templates, though it can be expanded upon
to:
!! Transactional Process
Like all editing in SeedCodeComplete13. Changes to status for Contacts and Projects are done in a modal edit mode. There is an On Save script trigger on the status fields:
->'''Contact Status On Save'''
->'''Project Status On Save'''
These scripts uses ExecuteSQL to look up the associated milestones and loads them into an array.
When the changes to the Contact or Project are complete and Save is pressed a sub-script is run called:
->'''Load Milestones Into Contact Events'''
->'''Load Milestones Into Contact Events'''
This script checks for the global variable created by the script trigger and asks the user if the associated milestones should be added to the project or contact.
Like all editing in SeedCodeComplete13. Changes to status for Contacts and Projects are done in a modal edit mode. There is an On Save script trigger on the status fields:
->'''Contact Status On Save'''
->'''Project Status On Save'''
These scripts uses ExecuteSQL to look up the associated milestones and loads them into an array.
When the changes to the Contact or Project are complete and Save is pressed a sub-script is run called:
->'''Load Milestones Into Contact Events'''
->'''Load Milestones Into Contact Events'''
This script checks for the global variable created by the script trigger and asks the user if the associated milestones should be added to the project or contact.
Changed lines 23-25 from:
-> Finally, the script asks if you'd like to apply any Process Templates tied to the new status.
to:
-> Finally, the script asks if you'd like to apply any Process Templates tied to the new status.
The contacts version of the script is much simpler and just looks for Process Templates, though it can be expanded upon.
The contacts version of the script is much simpler and just looks for Process Templates, though it can be expanded upon.
Added lines 3-4:
'''Overview'''
Changed lines 11-23 from:
Learn more about all this here: [[Milestone Templates]]
to:
Learn more about all this here: [[Milestone Templates]]
'''Scripts'''
Both the contact and project status fields have OnObjectModify script triggers tied to them. In Contacts this calls the script "Contact Status Changed" and in projects the trigger calls "Project Status Changed"
This project script "Project Status Changed" does several things:
-> After some statuses are selected it asks if we should stop logging time on the project. The lists of statuses which do this is configurable at the beginning of this script.
-> The script can email project staff and/or project contacts about the status change. A switch to enable this is found in the script after the comment "Emails all staff on the project when status changes".
-> Finally, the script asks if you'd like to apply any Process Templates tied to the new status.
'''Scripts'''
Both the contact and project status fields have OnObjectModify script triggers tied to them. In Contacts this calls the script "Contact Status Changed" and in projects the trigger calls "Project Status Changed"
This project script "Project Status Changed" does several things:
-> After some statuses are selected it asks if we should stop logging time on the project. The lists of statuses which do this is configurable at the beginning of this script.
-> The script can email project staff and/or project contacts about the status change. A switch to enable this is found in the script after the comment "Emails all staff on the project when status changes".
-> Finally, the script asks if you'd like to apply any Process Templates tied to the new status.
Changed lines 1-9 from:
to:
!! Linking a Process Template to a Status
Each process template can be linked to one or more statuses. In this way, when a contact's or project's status changes the software can add milestones from the linked template(s) to that contact or project.
Note that a template may be linked to more than one status, and a given status may be tied to more than one template.
When a user changes a contact or project status, and that status is tied to one or more templates, they are presented with a dialog asking if they'd like to apply the template's milestones to the project.
Learn more about all this here: [[Milestone Templates]]
Each process template can be linked to one or more statuses. In this way, when a contact's or project's status changes the software can add milestones from the linked template(s) to that contact or project.
Note that a template may be linked to more than one status, and a given status may be tied to more than one template.
When a user changes a contact or project status, and that status is tied to one or more templates, they are presented with a dialog asking if they'd like to apply the template's milestones to the project.
Learn more about all this here: [[Milestone Templates]]
