Versions Compared

Old Version 7

changes.mady.by.user Dev Raj Gautam

Saved on

compared with

New Version Current

changes.mady.by.user Dev Raj Gautam

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleWorkflow Studio Folder Structure

As a reminder, when you install Workflow Studio on your workstation, the installer creates a root TheDotNetFactory folder with two subfolders sub folders named EmpowerID and WFS. The EmpowerID folder contains required assemblies and executables executable for running Workflow Studio, while the WFS folder contains stock EmpowerID assemblies and product packages. These folders are linked to a Git repository or other form of source control. The content of these folders should not be modified. New development work occurs in the folders designated for such.

The below image shows how the folders are structured in an organization’s source control. The folders with black text are the folders that can be updated with custom content.

Note

Folders prefixed with an underscore, such as the _PublishedItems folder do not show in the source control tree on a developer's machine. This allows developers to create their own prefixed folders for the content they want to keep local to their personal development environment.

  • EmpowerID — This is the root installation folder. (Note that this folder should not be the root of the source control).

  • EmpowerID.Web.Overrides and EmpowerID.Web.CDN/Overrides — These folders are where Web customizations, such as .CSHTML pages and CSS files, are saved.

  • WFS/_assemblies — This folder contains assemblies for published custom Workflow Studio items.

  • WFS/_PublishedItems — This folder stores .pub files for any published custom Workflow Studio items.

  • Custom Folder — This folder represents any custom folders you add to the Source Control tree in Solution Explorer.

  • _Custom Folder — This folder represents any custom folders you add to the WFS folder that you do not want to appear in the Source Control tree.

...

When you are ready to deploy your development work to a testing or production environment, you log in to the EmpowerID Web interface for that environment as a user with the appropriate access to run the PublishWorkflowStudioItem workflow and upload the .pub file for the workflows or other objects you want to publish. Once the workflow completes the publishing process, your work is available to users in the environment. For more information, see Deploy to EmpowerID Environment.

Create and update manifest files

...

Batch deploy to local folders

Deploy to EmpowerID environment

Create a manifest file

Build a manifest file

...