{"id":547,"date":"2016-09-21T16:38:43","date_gmt":"2016-09-21T04:38:43","guid":{"rendered":"http:\/\/help.psoda.com\/?page_id=547"},"modified":"2020-11-26T16:18:58","modified_gmt":"2020-11-26T03:18:58","slug":"a370","status":"publish","type":"page","link":"https:\/\/www.psoda.com\/help\/a370\/","title":{"rendered":"Workflows"},"content":{"rendered":"
\"Workflow<\/a>Workflows are used to define the stages (or states) through which other assets go, as well as the \"Request<\/a>transitions between those states.\r\n\r\nPsoda contains a set of default workflows. These are fairly generic with no restrictions on transitions between states. If you would like to enforce a particular workflow then you have to add alternative workflows within your \"Contact<\/a>organisation.\r\n\r\nWorkflows can be added for an organisation, for a particular \"Programme<\/a>programme, for a particular \"Product<\/a>product or for a particular \"Project<\/a>project. A workflow will only be “visible” to children of its its parent asset.\r\n\r\nA workflow can be specific to specific type of asset, a group of asset types or to all assets. You can select the types that a workflow applies to when you \"Add<\/a>add or \"Edit<\/a>edit the workflow.\r\n\r\nA workflow can be in one of the following states:\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
State<\/th>\r\nDescription<\/th>\r\n<\/tr>\r\n
New<\/strong><\/td>\r\nThe default state for a new workflow.<\/td>\r\n<\/tr>\r\n
Modified<\/strong><\/td>\r\nThe default state when a workflow is modified.<\/td>\r\n<\/tr>\r\n
Reviewed<\/strong><\/td>\r\nIndicates that the workflow has been reviewed.<\/td>\r\n<\/tr>\r\n
Active<\/strong><\/td>\r\nIndicates that the workflow is active. This is the only state that the workflow will be “visible” to other children of the workflow’s parent asset.<\/td>\r\n<\/tr>\r\n
Suspended<\/strong><\/td>\r\nUsed to suspend a workflow. In this state the workflow will not be “visible” to other assets.<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table><\/div>\r\n

Related topics<\/h4>\r\n