& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
In this lesson, we’ll introduce you to how to create a new Tenant workflow. We’ll also demonstrate the basics of how to version, publish and delete workflows. Everything demonstrated in this lesson is applicable to all workflow types. Specific workflows are demonstrated in other courses.
Before you start modeling workflows in Upchain, we recommend that you already have a process in mind. Mapping this process out on paper, in a document, or in a diagram application gives you a solid base from which to start.
Make sure to include all the steps in your ideal process (happy path) as well as any possible roadblocks (exception path) that may occur. You should also note who will be responsible for each step and if any additional actions should occur, such as email notifications or status updates.
In this video, we’ll show you how to create a new Tenant workflow, both from scratch and using a System workflow as a base, and how to add and connect primitives.
Transcript
00:09
In this video, we'll show you how to create a new tenant workflow,
00:13
both from scratch and using a system workflow as a base, and how to add and connect primitives.
00:19
So, let's take a look.
00:22
Remember that system workflows are those provided out of the box and cannot be edited or deleted.
00:29
However, they can be duplicated to a tenant workflow so that you can use it as a base when creating your own workflow.
00:36
If you would like to model your tenant workflows based on the system workflows, you can duplicate them.
00:42
This means that you would not be starting from scratch.
00:46
This can be useful if you know that you only need to make minor changes to the system workflow to suit your needs,
00:52
or if you at least wish to keep what's already there in the system workflow to use as a base.
00:59
To duplicate a system workflow, make sure you're in the System Workflows section.
01:08
Then, click the drop-down menu of workflows, hover your cursor over the desired object, and then click on the workflow that you wish to duplicate.
01:20
This loads the workflow into the viewer.
01:25
Then click on the Duplicate as tenant workflow button.
01:31
Type in a name for your tenant workflow.
01:38
Click the "Duplicate" button.
01:43
The workflow is copied into the tenant workflow section and appears under its relevant object.
01:53
Note that you can change the name here if you made a mistake or a typo or decide on a different name.
02:01
Simply edit the workflow, type in the name, and then save the changes.
02:08
You can now begin editing this duplicated workflow that you just created.
02:15
You can also create your own workflows from scratch if desired.
02:19
You might choose to do this if the workflow you would like to create is completely different from the system workflows available.
02:27
To create a workflow from scratch, make sure you're in the Tenant Workflows section, then click the Create workflow button.
02:34
This opens the Create workflow window.
02:38
Give your new workflow a name.
02:42
The workflow type is already set to tenant, you cannot change this.
02:47
Select the objects.
02:48
This is the object the workflow is for.
02:51
Choose from eight different objects.
02:55
If applicable, select an object type.
02:58
This would be available for objects that have subtypes, including project types, custom task types, or custom business process types.
03:08
Note that these subtypes must already be created before you can create a workflow for it.
03:14
This is because you cannot change the object or object type once the workflow is created.
03:25
If applicable, import an XML file.
03:28
You would only use this if you already had a workflow exported to an XML file.
03:33
This might happen if you saved one as a backup or exported one from another tenant.
03:41
Click the "Save" button.
03:44
Your workflow is created and is loaded into the workflow viewer.
03:47
At this point, the workflow is completely empty, since we started from scratch.
03:52
But you can now begin to build your workflow.
03:57
Now that you have a new tenant workflow created, you have one for the task object with primitives already in it,
04:06
and you have one for the requirements object that we just created from scratch that's empty,
04:13
you can begin adding primitives and configuring the workflow to your liking.
04:18
You can do this for any workflow as long as the version is still in a draft state.
04:25
To begin editing the workflow, click the "Edit" button beside the workflow name.
04:31
This now locks the workflow to you and no one else can edit it.
04:35
You can see your name here.
04:39
Also, notice that a new workflow always begins at version 0.
04:44
Just like many other objects in Upchain, you can create multiple versions of a workflow,
04:48
but note that only one version can be published at any one time.
04:52
But we'll discuss versioning and publishing in another video.
04:58
Now, you can begin performing the following actions.
05:03
You can add a primitive by dragging it from the left menu and dropping it onto the canvas.
05:09
You may wish to begin with the start and stop primitives since all workflows need those.
05:17
There are two types of primitives.
05:18
You have user primitives, which require user input to proceed.
05:23
And there are system primitives that perform their task according to their settings.
05:31
Notice also that as you add new primitives to the canvas, it is assigned a number.
05:37
This is just its ID and does not affect the order in which the primitives are performed.
05:43
This is still controlled by you when you add the connectors between the primitives.
05:49
We're going to add a few more primitives: an update primitive, a task primitive, and a decision primitive.
05:58
And notice the numbers incrementing for each one.
06:04
Now, you can edit a primitive settings.
06:07
Refer to the Upchain help documentation for information on each specific primitive settings.
06:14
Any settings that are mandatory are highlighted with an asterisk.
06:18
We're going to configure the task primitive here.
06:24
It is a user task and this task will be to gather the requirements.
06:34
We will assign it to the workflow assignee.
06:41
The task needs a description to help the assignee know what to do.
06:46
And it's also useful to make sure to send an email notification so that they are notified when they have an assigned task.
06:55
And it's also useful to allow workflow cancellation.
07:02
Let's also configure the update primitive.
07:04
This will update the status of the requirement.
07:10
We'll mark this as in progress.
07:13
And we'll configure this first decision task.
07:16
This will be for the PM approval stage, the project manager approval stage.
07:26
Because it is a decision, they need a button to either approve or reject.
07:32
At this stage, again, we'll insert a description so the project manager knows what to do.
07:41
And we'll assign it to the project manager on the project team.
07:52
You can also clone a primitive by clicking on the primitive and then clicking the clone button.
08:01
This is quite useful if you already have a primitive configured and you wish to reuse it again with very similar settings.
08:10
So, we'll clone a couple additional update primitives as well.
08:25
And we'll clone the decision primitive one more time.
08:39
If you've added primitives by mistake, you can always remove them.
08:44
To do this, you would highlight the primitive by clicking on it and then click the "Delete" button.
08:51
You can also press the delete key on your keyboard.
08:54
This same process is used to delete connectors between the primitives as well.
09:04
Now, let's finish configuring these primitives.
09:11
The second decision task is for the customer to approve.
09:15
Most of the settings are the same.
09:16
This is why we cloned it.
09:18
And we'll assign this decision to the customer manager to approve the requirements on behalf of the customer.
09:29
And, lastly, if the requirement is approved, we'll set it to passed.
09:34
And let's save our work.
09:36
So, so far, we've added all the primitives we've needed, configured their settings, cloned some of them, and we've removed any unnecessary ones.
09:46
Now, let's connect the primitives together to show the order in which the primitives are meant to be performed.
09:53
To do this, you hover your mouse over a connector square,
09:58
click and drag your mouse until your cursor is over the next connector primitive, and then release your mouse button.
10:09
You always configure the happy path first, and then you would configure any exception paths second.
10:21
The decision primitives have two possible outcomes.
10:25
They can either approve or reject.
10:28
We've already connected the happy path if they approve.
10:31
Now we need to decide what to do if they reject.
10:36
So, to do that, again, hover your mouse over a connector, click and drag, and you'll notice the path is red this time.
10:45
If you've done this incorrectly, you can highlight that connector and then press the delete key and try again.
10:54
So, in this case, if either the project manager or customer rejects the requirements,
11:02
we're going to send the workflow back to the beginning, and the task will be reassigned to the work order assignee to try again.
11:13
So, it is entirely up to you how you wish to approach the creation of the workflow.
11:17
You might find it easiest to add all primitives first, configure their settings, and then connect them all together at the end.
11:25
Keep in mind that a workflow is linear.
11:28
You cannot create separate branches to be followed simultaneously.
11:32
So, for instance, if you have multiple decisions, they must be completed one at a time consecutively.
11:39
At frequent intervals, as just demonstrated, you should save the workflow.
11:45
This is so that if you lose Internet connection or something goes wrong with your computer, you have not lost any of your work.
11:54
To continue editing, you would then click the "Edit" button beside the "Workflow Name" once more.
12:00
Now that you know how to create your own workflows, keep going to learn how to manage their versions, how to publish them, and more.
Video transcript
00:09
In this video, we'll show you how to create a new tenant workflow,
00:13
both from scratch and using a system workflow as a base, and how to add and connect primitives.
00:19
So, let's take a look.
00:22
Remember that system workflows are those provided out of the box and cannot be edited or deleted.
00:29
However, they can be duplicated to a tenant workflow so that you can use it as a base when creating your own workflow.
00:36
If you would like to model your tenant workflows based on the system workflows, you can duplicate them.
00:42
This means that you would not be starting from scratch.
00:46
This can be useful if you know that you only need to make minor changes to the system workflow to suit your needs,
00:52
or if you at least wish to keep what's already there in the system workflow to use as a base.
00:59
To duplicate a system workflow, make sure you're in the System Workflows section.
01:08
Then, click the drop-down menu of workflows, hover your cursor over the desired object, and then click on the workflow that you wish to duplicate.
01:20
This loads the workflow into the viewer.
01:25
Then click on the Duplicate as tenant workflow button.
01:31
Type in a name for your tenant workflow.
01:38
Click the "Duplicate" button.
01:43
The workflow is copied into the tenant workflow section and appears under its relevant object.
01:53
Note that you can change the name here if you made a mistake or a typo or decide on a different name.
02:01
Simply edit the workflow, type in the name, and then save the changes.
02:08
You can now begin editing this duplicated workflow that you just created.
02:15
You can also create your own workflows from scratch if desired.
02:19
You might choose to do this if the workflow you would like to create is completely different from the system workflows available.
02:27
To create a workflow from scratch, make sure you're in the Tenant Workflows section, then click the Create workflow button.
02:34
This opens the Create workflow window.
02:38
Give your new workflow a name.
02:42
The workflow type is already set to tenant, you cannot change this.
02:47
Select the objects.
02:48
This is the object the workflow is for.
02:51
Choose from eight different objects.
02:55
If applicable, select an object type.
02:58
This would be available for objects that have subtypes, including project types, custom task types, or custom business process types.
03:08
Note that these subtypes must already be created before you can create a workflow for it.
03:14
This is because you cannot change the object or object type once the workflow is created.
03:25
If applicable, import an XML file.
03:28
You would only use this if you already had a workflow exported to an XML file.
03:33
This might happen if you saved one as a backup or exported one from another tenant.
03:41
Click the "Save" button.
03:44
Your workflow is created and is loaded into the workflow viewer.
03:47
At this point, the workflow is completely empty, since we started from scratch.
03:52
But you can now begin to build your workflow.
03:57
Now that you have a new tenant workflow created, you have one for the task object with primitives already in it,
04:06
and you have one for the requirements object that we just created from scratch that's empty,
04:13
you can begin adding primitives and configuring the workflow to your liking.
04:18
You can do this for any workflow as long as the version is still in a draft state.
04:25
To begin editing the workflow, click the "Edit" button beside the workflow name.
04:31
This now locks the workflow to you and no one else can edit it.
04:35
You can see your name here.
04:39
Also, notice that a new workflow always begins at version 0.
04:44
Just like many other objects in Upchain, you can create multiple versions of a workflow,
04:48
but note that only one version can be published at any one time.
04:52
But we'll discuss versioning and publishing in another video.
04:58
Now, you can begin performing the following actions.
05:03
You can add a primitive by dragging it from the left menu and dropping it onto the canvas.
05:09
You may wish to begin with the start and stop primitives since all workflows need those.
05:17
There are two types of primitives.
05:18
You have user primitives, which require user input to proceed.
05:23
And there are system primitives that perform their task according to their settings.
05:31
Notice also that as you add new primitives to the canvas, it is assigned a number.
05:37
This is just its ID and does not affect the order in which the primitives are performed.
05:43
This is still controlled by you when you add the connectors between the primitives.
05:49
We're going to add a few more primitives: an update primitive, a task primitive, and a decision primitive.
05:58
And notice the numbers incrementing for each one.
06:04
Now, you can edit a primitive settings.
06:07
Refer to the Upchain help documentation for information on each specific primitive settings.
06:14
Any settings that are mandatory are highlighted with an asterisk.
06:18
We're going to configure the task primitive here.
06:24
It is a user task and this task will be to gather the requirements.
06:34
We will assign it to the workflow assignee.
06:41
The task needs a description to help the assignee know what to do.
06:46
And it's also useful to make sure to send an email notification so that they are notified when they have an assigned task.
06:55
And it's also useful to allow workflow cancellation.
07:02
Let's also configure the update primitive.
07:04
This will update the status of the requirement.
07:10
We'll mark this as in progress.
07:13
And we'll configure this first decision task.
07:16
This will be for the PM approval stage, the project manager approval stage.
07:26
Because it is a decision, they need a button to either approve or reject.
07:32
At this stage, again, we'll insert a description so the project manager knows what to do.
07:41
And we'll assign it to the project manager on the project team.
07:52
You can also clone a primitive by clicking on the primitive and then clicking the clone button.
08:01
This is quite useful if you already have a primitive configured and you wish to reuse it again with very similar settings.
08:10
So, we'll clone a couple additional update primitives as well.
08:25
And we'll clone the decision primitive one more time.
08:39
If you've added primitives by mistake, you can always remove them.
08:44
To do this, you would highlight the primitive by clicking on it and then click the "Delete" button.
08:51
You can also press the delete key on your keyboard.
08:54
This same process is used to delete connectors between the primitives as well.
09:04
Now, let's finish configuring these primitives.
09:11
The second decision task is for the customer to approve.
09:15
Most of the settings are the same.
09:16
This is why we cloned it.
09:18
And we'll assign this decision to the customer manager to approve the requirements on behalf of the customer.
09:29
And, lastly, if the requirement is approved, we'll set it to passed.
09:34
And let's save our work.
09:36
So, so far, we've added all the primitives we've needed, configured their settings, cloned some of them, and we've removed any unnecessary ones.
09:46
Now, let's connect the primitives together to show the order in which the primitives are meant to be performed.
09:53
To do this, you hover your mouse over a connector square,
09:58
click and drag your mouse until your cursor is over the next connector primitive, and then release your mouse button.
10:09
You always configure the happy path first, and then you would configure any exception paths second.
10:21
The decision primitives have two possible outcomes.
10:25
They can either approve or reject.
10:28
We've already connected the happy path if they approve.
10:31
Now we need to decide what to do if they reject.
10:36
So, to do that, again, hover your mouse over a connector, click and drag, and you'll notice the path is red this time.
10:45
If you've done this incorrectly, you can highlight that connector and then press the delete key and try again.
10:54
So, in this case, if either the project manager or customer rejects the requirements,
11:02
we're going to send the workflow back to the beginning, and the task will be reassigned to the work order assignee to try again.
11:13
So, it is entirely up to you how you wish to approach the creation of the workflow.
11:17
You might find it easiest to add all primitives first, configure their settings, and then connect them all together at the end.
11:25
Keep in mind that a workflow is linear.
11:28
You cannot create separate branches to be followed simultaneously.
11:32
So, for instance, if you have multiple decisions, they must be completed one at a time consecutively.
11:39
At frequent intervals, as just demonstrated, you should save the workflow.
11:45
This is so that if you lose Internet connection or something goes wrong with your computer, you have not lost any of your work.
11:54
To continue editing, you would then click the "Edit" button beside the "Workflow Name" once more.
12:00
Now that you know how to create your own workflows, keep going to learn how to manage their versions, how to publish them, and more.
In this video, we’ll demonstrate the basics of how to manage your workflows, including versioning, publishing, and deleting.
Transcript
00:10
In this video, we'll demonstrate the basics of how to manage your workflows, including versioning, publishing, and deleting.
00:18
So, let's take a look.
00:22
Remember that a brand-new workflow always begins at version 0.
00:28
Once you've configured a workflow, in order for your team to be able to use it, it must be published.
00:35
Publishing a workflow makes it active.
00:37
After that, if you need to make further changes to the workflow, you'll need to make a new version of it.
00:45
This new version is in a draft state and can be edited.
00:49
Once completed, you can then publish the new workflow version,
00:53
and you can repeat this as many times as necessary until you obtain your desired workflow.
01:01
All versions of the workflow are still maintained and can be viewed, exported to an XML file, or published,
01:09
but only one version can be published at a time.
01:12
All other versions that are not published have a status of Draft or Obsolete.
01:18
However, you can make any previous version active at any time.
01:23
So, let's explore this.
01:27
To publish a specific workflow version, first load that version you wish to publish into the workflow viewer, then click the "Publish" button.
01:39
Upchain always performs a sanity check on the workflow to ensure you have not missed any necessary settings in the primitives,
01:47
and that all necessary connections between the primitives have been made.
01:51
This is to ensure you do not publish something that does not have all necessary logic in place to handle all possible outcomes of the workflow.
02:01
If Upchain detects any errors or missing information in your workflow,
02:06
it'll provide you with a message in the top right corner indicating which primitives need attention.
02:12
In this example, primitive 5 is missing its exception connector,
02:17
so let's put that in, save our changes,
02:26
and we should be able to publish it successfully now.
02:31
There we go.
02:33
Now, version 1 is published.
02:38
You can only have one version published at a time, but you can make any version active at any time.
02:45
To publish a different version, select that version from the drop down to load it into the workflow viewer and then click the Publish button.
02:55
Again, Upchain has performed its sanity check, so let's just edit that, save the changes, and now we can publish it.
03:10
And now the published version is 0.
03:15
Version 1 that was previously published now has a status of obsolete.
03:22
So, to summarize the different statuses, published means it is active for the end user.
03:29
Draft means it can still be edited.
03:32
And obsolete means it was previously published but is no longer active and can no longer be edited.
03:39
Some things to note.
03:40
If there was already another version published, it would become obsolete and the chosen version becomes published.
03:46
This means that the new version immediately becomes available to select, and the old version is no longer available.
03:54
If a previous workflow version is already in progress, when it is made obsolete, it still continues as is until completed or canceled.
04:04
Users may receive a warning that their workflow version is no longer active if there's a task they need to perform,
04:11
but otherwise, it will still progress as normal.
04:14
This just prevents objects getting stuck in the middle of a workflow that is suddenly made obsolete.
04:21
That won't happen.
04:25
When a workflow is first created, it's at version 0.
04:32
If you wish to make another version, maybe because you didn't like version 0,
04:37
and wish to start again or because version 0 is published and requires edits, there are several ways to do this.
04:46
First, load the workflow version that you would like to version into the workflow viewer.
04:54
Click the "Menu" button, and now you have three options to make a new version.
05:02
You can choose Import as new version.
05:05
This allows you to import an XML file as the new version of the workflow,
05:10
and it doesn't matter if the new version is a completely different structure from the current one.
05:16
You might have this XML file from a backup you made earlier or from a different tenant.
05:26
You could select new version.
05:30
This creates a new version of the workflow that is completely blank.
05:35
You would only use this option if you wished to start again from scratch but maintain the workflow name.
05:41
This will completely wipe out the workflow in the next version.
05:48
And, lastly, you could choose Save as New Version.
05:52
This is the option you'll likely use most often.
05:56
This simply takes the loaded version of the workflow and copies it into a new version.
06:02
So, let's demonstrate that one.
06:05
So, version 1 already existed, so it created version 2, and it is identical to version 0 currently.
06:16
And it's in a draft state so that we can edit it if needs be.
06:23
So, in each of the above options, the new versions are created,
06:27
with whichever the next available number is, loaded into the viewer, and put into a draft state.
06:34
You can then begin to edit that workflow version to make whatever changes it is you need to make.
06:43
If you no longer wish to use or keep a workflow, you can delete it.
06:49
This is one of the rare locations within Upchain that allows you to delete something.
06:56
We recommend though that before you delete anything, you first export this workflow to an XML file in case you wish to restore it again later.
07:11
To delete a workflow, load any version of it into the workflow viewer.
07:20
Click the menu button and select delete.
07:25
Confirm that you wish to permanently delete the workflow.
07:36
So, what's just happened?
07:38
All versions of the workflow are deleted and can no longer be found in the drop-down menu.
07:45
If a version of the workflow was still in progress, it still continues as is until completed or canceled.
07:52
Users may receive a warning that their workflow version is no longer active if there's a task to perform.
07:58
But otherwise, it will still progress as normal.
08:01
Again, this is just to prevent objects getting stuck in the middle of a workflow if it suddenly becomes obsolete or deleted.
08:10
That won't happen.
08:16
So, these series of videos should put you in a good position to get started in creating and managing your own workflows.
08:24
You'll notice that we didn't focus on one specific workflow type because every workflow is configured and managed in the same way.
08:32
What's different, of course, is the available primitives for each workflow type and what each workflow type can do for you specifically.
08:42
Subsequent courses will introduce you to some more specific workflows,
08:46
and provide realistic examples of the sorts of things you may choose to include in your workflows.
08:52
So, keep going.
Video transcript
00:10
In this video, we'll demonstrate the basics of how to manage your workflows, including versioning, publishing, and deleting.
00:18
So, let's take a look.
00:22
Remember that a brand-new workflow always begins at version 0.
00:28
Once you've configured a workflow, in order for your team to be able to use it, it must be published.
00:35
Publishing a workflow makes it active.
00:37
After that, if you need to make further changes to the workflow, you'll need to make a new version of it.
00:45
This new version is in a draft state and can be edited.
00:49
Once completed, you can then publish the new workflow version,
00:53
and you can repeat this as many times as necessary until you obtain your desired workflow.
01:01
All versions of the workflow are still maintained and can be viewed, exported to an XML file, or published,
01:09
but only one version can be published at a time.
01:12
All other versions that are not published have a status of Draft or Obsolete.
01:18
However, you can make any previous version active at any time.
01:23
So, let's explore this.
01:27
To publish a specific workflow version, first load that version you wish to publish into the workflow viewer, then click the "Publish" button.
01:39
Upchain always performs a sanity check on the workflow to ensure you have not missed any necessary settings in the primitives,
01:47
and that all necessary connections between the primitives have been made.
01:51
This is to ensure you do not publish something that does not have all necessary logic in place to handle all possible outcomes of the workflow.
02:01
If Upchain detects any errors or missing information in your workflow,
02:06
it'll provide you with a message in the top right corner indicating which primitives need attention.
02:12
In this example, primitive 5 is missing its exception connector,
02:17
so let's put that in, save our changes,
02:26
and we should be able to publish it successfully now.
02:31
There we go.
02:33
Now, version 1 is published.
02:38
You can only have one version published at a time, but you can make any version active at any time.
02:45
To publish a different version, select that version from the drop down to load it into the workflow viewer and then click the Publish button.
02:55
Again, Upchain has performed its sanity check, so let's just edit that, save the changes, and now we can publish it.
03:10
And now the published version is 0.
03:15
Version 1 that was previously published now has a status of obsolete.
03:22
So, to summarize the different statuses, published means it is active for the end user.
03:29
Draft means it can still be edited.
03:32
And obsolete means it was previously published but is no longer active and can no longer be edited.
03:39
Some things to note.
03:40
If there was already another version published, it would become obsolete and the chosen version becomes published.
03:46
This means that the new version immediately becomes available to select, and the old version is no longer available.
03:54
If a previous workflow version is already in progress, when it is made obsolete, it still continues as is until completed or canceled.
04:04
Users may receive a warning that their workflow version is no longer active if there's a task they need to perform,
04:11
but otherwise, it will still progress as normal.
04:14
This just prevents objects getting stuck in the middle of a workflow that is suddenly made obsolete.
04:21
That won't happen.
04:25
When a workflow is first created, it's at version 0.
04:32
If you wish to make another version, maybe because you didn't like version 0,
04:37
and wish to start again or because version 0 is published and requires edits, there are several ways to do this.
04:46
First, load the workflow version that you would like to version into the workflow viewer.
04:54
Click the "Menu" button, and now you have three options to make a new version.
05:02
You can choose Import as new version.
05:05
This allows you to import an XML file as the new version of the workflow,
05:10
and it doesn't matter if the new version is a completely different structure from the current one.
05:16
You might have this XML file from a backup you made earlier or from a different tenant.
05:26
You could select new version.
05:30
This creates a new version of the workflow that is completely blank.
05:35
You would only use this option if you wished to start again from scratch but maintain the workflow name.
05:41
This will completely wipe out the workflow in the next version.
05:48
And, lastly, you could choose Save as New Version.
05:52
This is the option you'll likely use most often.
05:56
This simply takes the loaded version of the workflow and copies it into a new version.
06:02
So, let's demonstrate that one.
06:05
So, version 1 already existed, so it created version 2, and it is identical to version 0 currently.
06:16
And it's in a draft state so that we can edit it if needs be.
06:23
So, in each of the above options, the new versions are created,
06:27
with whichever the next available number is, loaded into the viewer, and put into a draft state.
06:34
You can then begin to edit that workflow version to make whatever changes it is you need to make.
06:43
If you no longer wish to use or keep a workflow, you can delete it.
06:49
This is one of the rare locations within Upchain that allows you to delete something.
06:56
We recommend though that before you delete anything, you first export this workflow to an XML file in case you wish to restore it again later.
07:11
To delete a workflow, load any version of it into the workflow viewer.
07:20
Click the menu button and select delete.
07:25
Confirm that you wish to permanently delete the workflow.
07:36
So, what's just happened?
07:38
All versions of the workflow are deleted and can no longer be found in the drop-down menu.
07:45
If a version of the workflow was still in progress, it still continues as is until completed or canceled.
07:52
Users may receive a warning that their workflow version is no longer active if there's a task to perform.
07:58
But otherwise, it will still progress as normal.
08:01
Again, this is just to prevent objects getting stuck in the middle of a workflow if it suddenly becomes obsolete or deleted.
08:10
That won't happen.
08:16
So, these series of videos should put you in a good position to get started in creating and managing your own workflows.
08:24
You'll notice that we didn't focus on one specific workflow type because every workflow is configured and managed in the same way.
08:32
What's different, of course, is the available primitives for each workflow type and what each workflow type can do for you specifically.
08:42
Subsequent courses will introduce you to some more specific workflows,
08:46
and provide realistic examples of the sorts of things you may choose to include in your workflows.
08:52
So, keep going.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.