Power up your PLM with ForgeFlow

GREG LEMONS: Good morning, everybody. Can you hear me? This is going to be a product demonstration of ForgeFlow. Is it too loud?

AUDIENCE: Nope.

GREG LEMONS: OK. I got past the class a little late, so I don't have a lot of the supporting information like a nice screen up there with my name and bio, but I'll tell you a little bit about myself. Greg Lemons is my name. I work for D3 Technologies. Been with him for about five years. I'm a full stack developer with them.

So what we're going to be presenting today is a application called ForgeFlow. It's a multitenant web application that fills some of the gaps that Autodesk PLM software, the Fusion 360 Manage software-- so adds some features, help some users to do some functions in a more efficient way. And so with that, we'll go ahead and get started if we're ready.

So this is ForgeFlow. Right off the bat, this is the dashboard of what a company would see that has a subscription with ForgeFlow. You can have multiple tenants registered. A tenant is a Fusion 360 Manage tenant.

So a lot of companies may have a sandbox, a development, a production. This allows you to manage all of those tenants with this one application. So I'm going to have to kind of sit here. My cord doesn't quite reach the podium, so I hope that's OK.

We're going to be working in a tenant that is one of our company tenants. And so you may be familiar with this. This is, of course, Fusion 360 Manage. And Fusion 360 Manage obviously allows you to have workspaces, build workflows around processes, and manage your items.

So ForgeFlow came about because we were doing the same things over and over again for customers with this PLM. And we ended up having to spin up backend resources, build out the application form. And it was such a repeatable process that we decided to build a framework around it.

So this is all hosted in the cloud. The work that gets done gets done on worker machines that can scale up in the background. So a lot of operations are longrunning and we don't want the user sitting there waiting for it to complete. So this allows it to go out of your infrastructure and select the cloud handle it.

So to start out with, there is-- we supply tools and features to interact with PLM, but we do need to expose the UI so that people can get to the items within our application. So there is a bit of a replication around viewing items in workspaces, but we give you a little bit different view on those items, more of a power view.

So I'm going to start by selecting that tenant that I've got up here in the other tab, this Team D3 Modern tenant. And with ForgeFlow, if you get here, you see, we've got an index page for that tenant that gives us all of the features-- or the tools that we can run on it.

Before I go through those tools, you see this little jump menu here. We can actually hop between the other tenants that we've got in the system. And by selecting it, you will-- I selected the same one. By selecting it, you'll see your context menu changes up here to let you know what tenant you're in.

And so we'll start with Workspaces since that is the most common thing with PLM. And as we go in here, this is a little bit different list than what you see in Fusion 360 Manage, which you come over here and go to Workspaces-- if you have a lot of workspaces, this can get a little unwieldy. I do this a bunch of times-- I don't know if anybody else does-- where you gotta back out and go find where the workspace is.

So the first thing that we do here is we just have a filtered list or a filterable list of the workspaces. So as we type in here, it'll filter out the different workspaces. So it's a little bit more of a power user view on your workspaces.

Within Workspaces, as you can see, it's showing us the category that it's in, and we have these options-- Views, Items, Item Definition, and Grid Definition. And I'll start with Views. Views in Fusion 360 Manage are defined at the Workspace level. And so you have different views here, you're probably familiar with this.

And within the product, you can view them, but you can't get them out very easily. So a lot of times, to integrate with other software, to share this data, we want to get it out. So the first thing I'll show you is the views. And you can see, these views are the same views that are in Fusion 360 Manage.

And so if you select them and do a view on this, you'll get that same view that you see in Fusion 360 Manage, but with a Export option. So we can export the entire view out to a spreadsheet. This is the first time you'll see that job worker happening. We have real-time messaging that the workers transmit back to the UI so that they know when that document has been generated.

And just to show you what that looks like. The one additional item that you get is the DMS ID. That's the unique identifier for every item in Fusion 360 Manage. Sometimes it's hard to get to through the UI. So when we export them out, you do get that as a first column. But then everything else is aligned to what that view definition is that was created in Fusion 360 Manage.

So this export is great to interact-- or to integrate with that data with other services or applications, but keep in mind, we'll use something similar. We have-- one of the tools is an item loader, and it also updates items as well.

And you can take this export that we just did and roundtrip it into the system, and it'll update anything that has a DMS ID associated with it. If there was a column in here without a DMS ID, it adds that as a new item to that workspace. And I'll show you that when we get to it. So that's views.

Now we also have within that workspace-- I'm going to go back to the same workspace I was working on. We have items. Now this is similar, except it just shows all the items in a workspace. So you get the descriptor and the category. And I'll talk about these links shortly here associated with each of the items. But this is similar to the view, but this is the system-generated view, basically.

You'll see a column here called F3M. That links directly to these items in Fusion 360 Manage. So if you need to hop over to that item, you can go directly to it via that quick link in Fusion 360 Manage. So since this is an application that runs outside of it, it's useful to be able to link back into those locations.

So the-- going back to-- this is exploring the workspaces. Nothing much new here. But if we look, we have Item Details-- you can click either here or this Item Details, this is a different view than what you see in Fusion 360 Manage. So in Fusion 360 Manage, we have-- let me open that one up again. You have this defined by your workspace manager. You have sections and you have the data in here.

As a developer and if you are integrating with other software, sometimes you need additional information that you don't see in here. The fields themselves actually have a field ID in the backend. Generally you have to go to the Workspace Manager, open up that workspace, and find that information in there.

So our view actually gives you a little bit more insight into that. Our item detail screen has the system fields, which are raw system fields-- a lot of times you won't see those in the UI.

These custom fields are the same as what you'll see in the UI except we've got them in a straight tabular view with a field IDs associated with them, as well as the data type, any validations that are on there, and then the raw value as Fusion 360 Manage sees it. So it's a little bit different view than this view.

And again, it's probably useful for those that-- maybe a power user or someone that is going to be using this data elsewhere and needs references to field IDs, data types, and things like that, we also give a quick view of the attachments and allow you to download the attachments out of Fusion 360 Manage as well.

Now going back to the workspace here, we just looked at items. Scripts are also associated with a workspace. We have JavaScript files in Fusion 360 Manage that you can access through the administration portal and it shows you all of the scripts you've got.

We actually define in this one the workspace-related scripts. So when we go in here, these are all the scripts that are associated with that workspace-- in this case, there's just one. But you would have-- a lot of times you'll have your own Edit and your own create scripts in here as well.

And we'll get to scripting a little bit more, , but I want to pass through this. We also have the item definition. So for a workspace, much like the item definition, the workspace's item definition is without values.

But if we look at it, it's a similar view to what we saw on the detail page. You get a little bit more of that metadata out here, whether it's computed or a derived field. And again, this is similar to that other view we looked at, just without the values because this is the workspace definition.

And then the other thing we have is the grid definition. All of the workspaces you can add a grid to that workspace, and this will define that-- the columns and rows in that grid, as well as data types, editability, and validation as well.

On the items, when we are looking at one of those lists of items, you can view the grid via this link here. Again, there's no grid rows to display on that one, but you can also download the grid as a spreadsheet as well. This is all live, by the way. I'm doing this demo with real data. And so a little risky, but I wanted to show you that how fast it works, the backend system is working on it as well. All right.

So the other thing within the items, if I actually go into one of the items here, a grid we just talked about, attachments can be done in any of these views. So the Item view and any of the views that you choose will come out and give you all of these options.

So for the attachments, you can simply attach by selecting this attachment on any one of these, and together, the backend workers will go ahead and attach each of those files to the items. This is also, though, drag and dropable. So you can just drag items onto any of these. And again, you get the same feature to be able to upload.

So a little bit faster than going into each item, going to the Attachments tab and hitting Upload. And we'll actually show you this operation in bulk later because that is probably the more useful one when you have a lot of attachments that need to go to Items in the workspace.

There's another option here, and you see, this icon indicates code. We allow ad hoc scripting against an item in Fusion 360 Manage. So inside Fusion 360 Manage, you have their built-in JavaScript files, and they have on-demand files that you can run on an item. But we wanted to offer more languages that you can run against an item.

So we offer ad hoc scripting using C#, JavaScript, or PowerShell. JavaScript is also in Fusion 360 Manage; however, it's an older ECMA-- or the specification is older, so you can't use a lot of the newer JavaScript features. Our JavaScript engine is the latest JavaScript engine, so you can use some of the newer JavaScript features that you can't use in Fusion 360 Manage.

Although it is run outside of Fusion 360 Manage. So we grab the item, we run whatever code you have associated with it within our cloud-based infrastructure, and then we update the item in Fusion 360 Manage with the result.

So we're looking here is actually a C# code. Hopefully this should blow some people's mind. You can have live C# code and run it. It'll actually compile, hot load, and then run this against the item. And it injects that item into this method. So if we look at this, I'm injecting the item itself and this tenant information. I'm going to very quickly do an update on this. In fact, I'll load up an existing script. And I'll run the script.

And so this is building that C# assembly. It builds it, loads it into the system, and then modifies that item. Now we didn't save that item. I just ran some c-sharp code on it and then didn't update it. So let me go ahead and update it now.

And now it did finish successfully, and you probably saw another notification pop up. Webhook trigger. Item update. So this tells us that, hey, you updated an item in that Fusion 360 Manage tenant. And we will touch on webhooks a little bit more in the future.

So I won't go through the other script types here, but we've got JavaScript. You get a nice little IDE that-- or IDE-like interface, I should say, that gives you some code coloring and things like that for JavaScript and PowerShell and C#.

So keep this in mind. We're building an action, if you will, on an item. And this will be important later when we get into some of the integration pieces.

All right, so I'm going to now go to the Users section. This just lists all of the users that are inside the Fusion 360 Manage tenant. And it gives you an option to get detailed information about each of these, and it is the raw view of their user information.

So may not be useful in that respect. However, we do offer this user report. And this, again, generates an Excel file with all of the users' information, but it also gives you the license type that they're using, last login, and last access time. And this is a useful report for admins of PLM.

All right. So we're going to go ahead and move over to the scripting side. So ForgeFlow gives us a unique way to access our scripts. These are the scripts that live inside Fusion 360 Manage. Sometimes they can be a lot. Like here, we have 492 of them.

We'd like to-- we like to take this stuff out of Fusion 360 Manage in some cases and put it in maybe a code repository. Maybe you want to track changes that you've been doing on your scripts, it's hard to do inside Fusion 360 Manage.

We had ended up coming up with a convention that will put the updates in the top of the script file as we change them. But if you can download those and keep them in a source repository, you can use those systems to track those changes and even revert to the previous ones if you need to.

So we offer the ability-- first of all, before I show you the download, you can look at any one of these scripts within Fusion 360 Manage in our little IDE viewer here. And so this will color-code your JavaScript and show you that file. You can't edit the scripts in here. Fusion 360 Manage only allows you to edit them in product.

One thing that we have done that's a little different, if you've ever worked with scripting in Fusion 360 Manage, you have supporting libraries. And they show up in the UI similar to this, but you can't drill into them. You have to go back to the scripting interface and go find that file and load it up. We offer little just hot links so that you can load up and see those libraries within the product itself.

So again, when you are coming into a tenant that may be other people have already worked on or something like-- this gives you a little bit easier way to find all of the related information without a lot of clicks.

And going back to scripting. We also then, again, offer this Download All the Scripts functionality. And I'm actually going to switch to a different tenant since we have 492 scripts in there, which is quite a lot. Here, we have 186, we'll go and download all these.

And so again, we'll submit it and the backend workers take over, and we'll start downloading each one of those JavaScript files. They do separate it by the script type. You can see on the right-hand side here, we have the script types. That's Fusion 360 Manage's categorization of those scripts.

And so there, it's downloaded all 186 of them. It gives them to us in a nice archive. And the archive is separated by the folder showing the type. And then inside, these are all of the actual JavaScript files that live within Fusion 360 Manage.

OK. So, the next thing we're going to get to are the actual tools. So the main reason that ForgeFlow came into being was for these tools and generally for us to do things in bulk. The APIs that they provide generally allow operation against one item.

And while you can do that over and over again, it takes up resources on your own machine if you're doing it and things like that. So we use the views that I showed earlier inside Fusion 360 Manage as a source of items. So those views can be filtered by any number of the columns, so you can limit that-- what comes out in that view, and we use that as the data source for our bulk operations.

So if you wanted to operate on, I need to update this value in this workspace for all the items that have changed since x date or something like that, you would create a view for that, and then that would be the source your bulk source of information that we're going to operate on.

So I'll start with the bulk on-demand scripts. So we viewed the workspace and I viewed the scripts in the workspace and you saw there was one in there, one script in there. That was an on-demand script. And many times we want to run that against a bunch of items, not just one item.

And so that's what the Bulk On-Demand Script tool does. It will take an on-demand script that Fusion 360 Manage has, take your view as your source of items, and run that script against every single item for you. So this is the UI, and you select the workspace that you are going to do the scripting on. You select the view that you want to use as your data source.

Now we do offer you the ability to preview that view. So as I selected the view, I have this Open View button which shows me the view. So I can review it and say, OK, yeah, that's right. There's 29 items there. And then you select the script. Again, this reaches into Fusion 360 Manage, looks for the scripts that you can run, and we have this one script called Add HTML, which is just updating one of the fields in that.

Some views, they can return multiple items that are the same. So depending on what you're filtering that you've selected within Fusion 360 Manage, you could have the same item returned multiple times. So we offer the only process unique items which won't run it against the same item more than once.

And then we do have error thresholds. So scripting can error out, as I'm sure everybody knows. So we do offer a threshold, and if the system reaches so many errors, it'll go ahead and cancel the job and let you know that there are issues there, and I'll go ahead enable this.

So once we've got all of our items selected, we can go ahead and run it. And again, this runs on the backend jobs, and you can see, it's processing those items. And since I do have a webhook on it, you see all of those webhook notifications come in. So this is telling us that we've updated each one of these items in that workspace, and then you get a running view of the number that it's done. And it finished successfully, so we'll dismiss them all.

That's a very powerful feature that our own team has used to manage our own clients. And when we decided that, wow, this tool is very useful for our clients themselves, again, this is getting a lot of use by them as well.

OK. So the next one is the Bulk Attachment Loader. We talked about how you can attach via ForgeFlow in those View lists, in the Item lists just by dragging them on or selecting that attachment. This allows you to upload an entire archive of attachments that you want applied to a workspace.

And in fact, you can go cross-workspace with this. You can have multiple workspaces in this large archive and it'll attach them across the board. As long as you follow the convention. So right now, the convention is within an archive, you have a folder that has your workspace ID and your DMS ID, that unique identifier for an item.

So if you have this convention set up-- we do have plans in the future to allow kind of a mapping interface for this if you wanted to use different values instead of the IDs, but let me show you an archive here. So I took these two folders. You can see, it's got a workspace ID, an underscore, and then a DMS ID. Inside here, there's a couple images in that one, there's a few attachments in that one.

And so these should assign those attachments to those items in Fusion 360 Manage. So I zipped up those into this sample archive, and just to show you those same folders in there. And so here, we can take this large archive-- in this case, I think it's only like 30 megs, but it could be gigs big. And this is a reasonable upload.

So this-- it's a large file and you got halfway through 1 gig, you can continue from where you left off. So I uploaded that to the system, but you do still have to submit it. And we have this option to delete existing files before attaching. This will actually delete the existing attachments on that item before it attaches the new ones. I'll go ahead and do that in this case because I think I've run this test before.

And then again, if that's all in place, we can submit it and we'll see the backend workers kick in. And it says we're going to be attaching five files. And it goes through and attaches each of those files. And I'll prove to you that those went in here.

So Johnny Cash was one of the ones that we updated with these attachments. So if we go look in the Attachment section, we can see the two images that I just attached. 9:57, 9/27, that's today. And then the other item-- I believe it was-- was it Baby Yoda? It wasn't Baby Yoda. That's a different one.

So that's the Bulk Attachment Loader. Very useful if you've got hundreds and hundreds of attachments that need to go up. That is too many clicks if you have to do it through the UI.

So another tool that we've got is the Bulk Item Loader. So I showed you that you can export views from this tool. It exports that additional column that is the unique ID of it. We can actually take that back into the system to do any updates to those items.

So on this one, I think I will play you a quick video of this. And curious if the audio will work. You're not getting that audio, are you? OK. I'll go ahead and talk over this as the video is playing.

So this is explaining, again, that you can get the items out of a view. And we're going to be selecting that same API testing workspace that I used previously. This one offers you a template that you can download. So if you're not rerunning that output into the system, you can just build a spreadsheet based off this template.

And the template really is just every field in that workspace in an Excel column. And as you add rows, it will add those items into the system.

And so this is the file that we're using to update in this case. You can see, we've got three DMS IDs that are in there, but one on the bottom is a new one because it doesn't have a DMS ID, so it's going to try to add that into the system.

And so we select that spreadsheet. There's a mapping interface that allows you to map the fields that it sees in the spreadsheet to the fields within Fusion 360 Manage if they don't match. If they match, it attempts to automap them. It's what you've seen here. It went ahead and automapped those fields because our column names were the same. But you can unmap them and then select a totally different field that you would like that value to go into in Fusion 360 Manage.

Again, when you're done, you have the option to validate your results. If you've got a lot of them, you may want to do a validation first to make sure that you haven't you don't get any errors or things like that. So you can see it, it went ahead and did the update, and again, you see the notifications-- the real-time notifications coming in.

AUDIENCE: You didn't have to DMS ID [INAUDIBLE]?

GREG LEMONS: So there is no DMS field in that workspace. So you could map it, though, to a single-line text field if you want to keep the DMS ID in a visible field. We've had a lot of people do that, yeah. Yeah, it's useful.

So another bulk tool we have is the Bulk Archive tool. This allows you to, in bulk, based on a view, delete a whole bunch of items out of the workspace. So again, especially during testing, I found-- and this was probably a tool I built just for myself, I think.

But as I'm testing and debugging these tools, I end up with a lot of extra items in a workspace and it's tedious to get rid of them one at a time. And so if you can build a view and it'll delete all the items from that view. And should I delete them all? Sure, why not?

AUDIENCE: That's always a good idea.

GREG LEMONS: We're live, why not? So we archive all those items. I think that was probably the last test I wanted to show on that workspace. So if we go back to this workspace now, you'll see, there's nothing in here. It's empty.

So again, another useful tool. It just saves time on a lot of them. So OK. So I did want to show our audit trail for all of these actions that we run. So you saw real-time notifications coming across, but guess what? Those are transient.

And based on network conditions, you very well could have missed one or something like that. So all of this is captured in the system. And so you do have a job screen that shows you all of the jobs that you ran, the result of them.

And if there was a result that you can download, it gives you that access to download them here as well. If there was an error associated with it, you do have a little bug icon that shows you any errors and you can delete these jobs as well if you need to. So that's a little audit trail.

With ForgeFlow, you have different levels of users. And so the admins for a company can view everybody's job log and everybody's information. The user itself really only sees his own job log. I do want to talk a little bit about the admin and the tenant registration portion.

So you saw we have all these tenants in here. To register a tenant, you supply-- it's pretty simple. The subdomain of the tenant, the name, a client ID, and a client secret. And this is a Forge app that you associate with Fusion 360 Manage.

You have to do that to integrate with the API and Fusion 360 Manage. So the Forge client ID generally gets whitelisted with the Fusion 360 Manage tenant. And that is really the only step you have to take before ForgeFlow can go-- can attach to that tenant.

We also have an impersonation. So every call that an API makes, it wants to know what user is actually making that call. And so you can actually add the email of the impersonated user here. And then all the calls are made by that user. Any of the audit trails within F3M, Fusion 360 Manage, show that user as the one that edited or changed that product at all. OK.

So the last piece I wanted to talk about is the integration features that we offer. And in fact, I'm going to touch on webhooks first, but hopefully you'll see how they go into the integration portion of it. So with Fusion 360 Manage and a lot of Autodesk products, they offer webhooks.

And this is us entering the newer digital world. We used to poll for data all the time, and every minute, every five minutes you're pulling for data, and it just kills me whenever I see that. We live in an event-driven world now, and most of the applications that we interact with have webhooks or something that you can get that event on.

And I don't see a lot of people taking advantage of it yet. And one is because it's hard to create the webhook in Fusion 360 Manage. There's no UI around it. So you have to of either have a developer do this for you or, like I did, build a tool that will allow you to build webhooks within this system.

We handle-- we have some operations when we get to integrations that we want to handle the webhooks, but sometimes you just need to build a webhook that goes somewhere else. Goes to Jitterbit, goes to some other system that you need to notify when an item has changed or updated in the workspace. So I'm going to go and show you the webhooks.

So you saw a couple of those webhook notifications come up on screen for us, and this is why they came up. So you can see here, I've got three webhooks currently on that workspace, 247, an item create, an item update, and then a workflow transition.

And so some of this data is where that webhook is being sent, and this is probably irrelevant to us, but I do want to show you how easy it is to create a webhook. You select the workspace that you want to create it on, you either select the event-- and these are the six different events that Fusion 360 Manage offers webhooks on. We'll just go on the Locked one.

Or you can select a transition. This reaches into the Fusion 360 Manage workflow and looks at all the transitions available to us and then lists them here. And you can, again, create a webhook that happens when that transition takes place in Fusion 360 Manage.

So it's as easy as this. It just created a lock event. So now if I locked an item, I would get a webhook sent to this endpoint. I'll delete that one because we don't need it. And I did show you this, but I'll show it again. When you are in an item-- and again, I'm going to edit this. Say, I'm just going to change that one Boolean value, and then if we go over here, you'll see how quickly that happens. It says, oh, we've got an update event.

So I want to explain how our webhooks work in this multi-tenant environment. One of the requirements that Autodesk has is that you respond to a webhook request within x number of seconds. So a lot of first passes that people will do is they'll do their logic in that webhook and then realize that, oh my gosh, Autodesk is mad at me because I'm taking too long for these things.

So we built a system-- I call it the webhook funnel, but we take every single webhook that hits any client that's using ForgeFlow into a scalable-- similar to a Lambda function in AWS or a-- can't remember the name in Azure, but the equivalent one in Azure, functions, Azure functions, and they just run like a method in the cloud, a single method.

And what this does is it just accepts a webhook from Autodesk, sends back, OK, we got it, and then it puts it on to a durable queue that we manage-- ForgeFlow manages-- that lives throughout lifetimes, lives throughout restarts, app domain restarts, all of that stuff, so it's a durable queue and we know that we've got that webhook in there. Whether it was processed by a worker or not, it's sitting in that queue ready to go.

And that has been one of the learn-by-failure examples of working with webhooks, and I think part of the reasons why a lot of people haven't embraced them yet. But we're going to change that, right? So one is building a UI around it so you can easily build them, and then capturing that information is the next step.

So you get a webhook and it sends out a notification, you saw the little notification in our system, but a lot of times you want to do something after that. If you're sending it to something like Jitterbit or another service, it's on that service's responsibility to do whatever you want to do afterwards.

But when you're within ForgeFlow, it knows the Autodesk products. And so we can build integrations around them. And so I talked to-- I showed you a little bit about the code that you can apply to each item. JavaScript, C#, or PowerShell. Showed you the webhooks. Hopefully maybe the picture's coming together that when a webhook hits, we can run an action based on that item. And so that is what ForgeFlow--

And this is actually a beta feature that I'm going to show you in integrations that is in our sandbox right now but will be pushed to production soon. And this is the integration projects. So within an integration, you generally have a trigger, something that starts it off, and then some actions that you want to do afterwards. This is our Integration Designer. And a little bit of overflow on my colors here.

So you define a trigger. And this could be an F3M webhook trigger or an external trigger, or again, just a recurring something you want to happen every x minutes or x hours. In this case, I have an Upchain ECR update here or webhook.

So one of the-- Upchain, as you all know, is the data side of the cloud PLM now. And they have limited webhooks, but one of them is for an ECR. So you can receive a webhook for that change request. And again, you may want to operate on that item in here.

So in our case, we may want to have that be a F3M webhook instead. And I'll delete this and just to show you how cool this little designer is. You can run operations in parallel. So maybe you've got something that's going to do a longrunning action to update an ERP, but you also want to maybe send out a team's message to people or anything else that you'd like to do.

So this is what the Integration Designer is for. And again, you can test-- do A/Bs. This parallel option that we offer here allows you to maybe turn off one track, run it, test it, maybe turn on the other track and test that, or have multiple A/B/Cs in here to do that.

And then again, we also offer the-- let me refresh this since I have this one set up-- the ability-- a little eye candy to show you the animation that the paths will take if you have that.

Again, some stuff that's probably not relevant, but you can change a lot of these UIs. You can change the Bezier curves of your connections if you wanted to, again, the color of all of the nodes and stuff. So not really functional, but makes some people happy when they see that.

Now these actions come from those scripts that you can build against each item. And the reason that code-- I'm going to go back to the items to show you that. The-- I'm going to pull up a view here and show you that little code string again. There's nothing in that view. I deleted everything in this tenant, didn't I? I sure did.

We're going to go to another tenant. And so this code-- the reason you can save these scripts is so that you can use them in that integration portion of the system. So you can-- when you add that node within our Integration Designer, you select which script it's going to run if it's a node that runs scripts.

And this is where you can build them, debug them, and test them against a single item in the workspace. So you can get your process or your script down and then bring it into the integration part. And I'm not going to demo that integration portion because I deleted all the items in that workspace, but that's what's coming.

And again, like I said, that Integration Designer is in beta right now. It's going to be released very soon. And I think that covers my demo. I wanted to leave about 15 minutes if we had any questions around ForgeFlow. So thank you very much for listening. So do we have any questions?

[APPLAUSE]

Mill.

AUDIENCE: Where's ForgeFlow [INAUDIBLE]?

GREG LEMONS: So right now, it's hosted in Azure. The workers themselves are independent of OS. So we can have them running in AWS, you can have client machines in your company logged on and acting as workers. But right now, they're scalable Azure machines.

AUDIENCE: Gotcha.

GREG LEMONS: Yep. Back in the back.

AUDIENCE: Hey, Greg. When you did the upload for the document, [INAUDIBLE] on FIFO and [INAUDIBLE] use an API [INAUDIBLE], do you have [INAUDIBLE] to do [INAUDIBLE] there?

GREG LEMONS: So I don't have any validation happening on there. So the 1-gig limit probably still lives. And in fact, you have other limits. So when you're uploading a file, Windows itself has a file size limitation. So that archive can only be, what, 2 gigabytes big at its maximum.

But I have tested-- in fact, I tested last night, I was with some-- at dinner with some people and they're like, can we upload a file? Because I believe the doc officially says 500 megabytes. And so I just proved out that through our system, it can actually upload up to 1 gigabyte-- I think I did a 750-meg file and it went through fine. But you are-- you do have those limitations on file sizes.

AUDIENCE: [INAUDIBLE] on the, I think, backend. I know inside of [INAUDIBLE] there is a timeout sequence.

GREG LEMONS: Right.

AUDIENCE: Are you going to hit that time [INAUDIBLE]?

GREG LEMONS: So when you're running on-demand scripts-- so we have the Bulk On-Demand Script tool which runs Fusion 360 Manage scripts and it runs within Fusion 360 Manage. So you are under that same six or nine-second limitation-- six.

And now, though those three-- our own JavaScript engine that ForgeFlow has up there and the PowerShell and the C# engine do not have that limitation. So there are-- you can do a very longrunning operation on any of those without worrying about the tenant crashing out on you.

In fact, it doesn't update the item until after its action is done. And so its actually interaction with Fusion 360 Manage is very short. Go ahead.

AUDIENCE: Is there a rollback feature for the bulk options?

GREG LEMONS: No. No, there's not. And I will caution people, when you're dealing with scripting-- and you probably already know this. When you're dealing with scripting within Fusion 360, there are things that can go wrong. And so that's why we try to build those individual one-offs so you can test your functionality before you go bulk with it. And that's the best we could do I think at this point based on Fusion 360 Manage's infrastructure.

AUDIENCE: [INAUDIBLE]

GREG LEMONS: Please.

AUDIENCE: Essentially when you become a ForgeFlow customer, part of the process and onboarding and training, you go over a process [INAUDIBLE], a process [INAUDIBLE]

GREG LEMONS: Right. Because you can't export these things and save them as a backup, and then maybe you would export a whole workspace, run your bulk operation, and go, oh, no, I messed up. Then you could delete all those and pull in your whole-- that exported list you have. Right.

So we try to give features to allow you to work through the problem if it's encountered. So any other questions? Yes?

AUDIENCE: Two questions. One, what can you do with the data archive? Secondly is how do you protect the customer's security?

GREG LEMONS: So the customer's client secret? So first of all, only admins can add them. And then if you look at them again we obfuscate the client secret just like they do in the UI for Forge. So we have asterisks there and you can't even inspect the page and see the real value it is, we don't even put the real value into the page. So that was the one. What was the other question?

AUDIENCE: What can you do with the archive data?

GREG LEMONS: Well, I mean, that is-- so for-- when you download an archive of scripts, generally, for us, we started it because we wanted to put it into an external system. And maybe you want to work on scripts in Visual Studio code instead of the IDE that is supplied with Fusion 360 Manage.

So those are two reasons that you can-- two ways that you can use that archive. But I think the primary one and probably the most useful one is to put it into a source code repository so that you can track the changes, revert back to old ones, and things like that to just manage your scripting. Yeah. Any other questions? All right. Well thank you, everybody, for your time.