DecisionFlow User Manual

{
  "company": "Acme Manufacturing",
  "industry": "Manufacturing",
  "employeeCount": 85,
  "annualRevenue": 2500000,
  "source": "Referral",
  "requestedDemo": true,
  "budgetConfirmed": true
}

"Hot Lead"

Getting Started

1. Open DecisionFlow in your browser.
2. Sign in with email/password or use Google Sign-In if enabled.
3. Complete multi-factor verification if required.
4. If you belong to more than one organization, choose the organization to work in.

If you received an invitation, use the invitation link to complete sign-up. If you forget your password, select Forgot Password on the sign-in page.

Roles and Permissions

Roles are assigned at the organization level. A user may have different roles in different organizations.

Admin

Full organization access. Admins can:

• Manage team members and invitations
• Manage organization auth tokens
• Create, edit, test, and version workflows
• Deploy and undeploy production versions
• Import and export workflows
• View audit logs
• Manage organization settings

Editor

Workflow development access. Editors can:

• Create workflows
• Edit workflows
• Test workflows
• Create and manage workflow versions
• View audit logs

Editors cannot:

• Deploy or undeploy workflows
• Import or export workflows
• Manage team members
• Manage organization auth tokens

Viewer

Read-only access. Viewers can:

• Browse workflows
• View workflow logic
• Review audit history
• Copy endpoint URLs

Viewers cannot:

• Create or edit workflows
• Test workflows
• Create versions
• Delete workflows
• Publish or deploy workflows

Note: Permissions apply per organization. A user may be an Admin in one organization and a Viewer or Editor in another.

Navigation

The sidebar is the primary way to move through DecisionFlow:

• Dashboard: Create, open, search, import, export, version, publish, and delete workflows.
  • Admins: Full workflow management
  • Editors: Create, edit, test, and version workflows
  • Viewers: Browse workflows and copy endpoint URLs
• Audit Logs: Review organization activity.
• Settings: Manage profile, team, security, and auth token settings.

For the lead scoring example, start on Dashboard to create a workflow. Return later to manage versions and publishing.

Organizations

DecisionFlow is multi-tenant. Each organization has its own workflows, users, audit logs, versions, and deployments. Use the organization switcher to move between orgs. Ensure you are in the org that owns the sales process and lead data.

Common roles

• Admin: Manages members, organization auth tokens, workflows, versions, and publishing.
• Editor: Creates and edits workflows when permitted.
• Viewer: Views data but cannot edit or publish.

Workflows

The Dashboard lists workflows for the selected organization. For the tutorial, create Lead Scoring Workflow.

Typical dashboard actions

• Search workflows; filter by status.
• Create a new workflow.
• Expand a workflow to inspect versions.
• Open for editing.
• Import or export workflow definitions.
• Copy endpoint URLs.
• Publish, unpublish, duplicate, or delete versions (when permitted).

Permissions

• Admins: Full workflow management, including import/export and deployment.
• Editors: Create, edit, test, and version workflows.
• Viewers: View workflow definitions and version history only.

Create the lead scoring workflow

1. Select Create New Workflow.
2. If prompted by the AI assistant, choose manual creation.
3. Name it Lead Scoring Workflow.
4. Open the Workflow Editor to configure the lead payload and scoring rule.

Workflow Editor

The editor is a visual canvas. A workflow begins with input data, evaluates rule nodes, and ends at a result.

Access Requirements

• Admins and Editors can modify workflow logic and save changes.
• Viewers can open workflows in read-only mode and cannot save changes.

Entering Lead Payload Steps

1. Configure the Start/Test Payload node with representative lead data.
   1. Click the Node
   2. Click the drop down arrow
   3. Click “Save as new Template” or leave as Custom
   4. Enter/Save Template Name
   5. Paste the below payload (JSON) into the following section

      

{
  "company": "Acme Manufacturing",
  "industry": "Manufacturing",
  "employeeCount": 85,
  "annualRevenue": 2500000,
  "source": "Referral",
  "requestedDemo": true,
  "budgetConfirmed": true
}

2. Click the PLUS to Add an EXECUTE rule node.

Entering Rule and Result Paths

Rule nodes contain business logic. DecisionFlow uses JSONata expressions for evaluation.

Lead scoring expression

(requestedDemo and budgetConfirmed and annualRevenue >= 1000000) ? "Hot Lead" : ((requestedDemo or source = "Referral") ? "Warm Lead" : "Nurture")

• Returns Hot Lead when the lead requested a demo, has confirmed budget, and revenue is at least 1,000,000.
• Returns Warm Lead when the lead requested a demo or came from a referral.
• Returns Nurture for lower-intent leads.

Create a clearly named result node for each possible output. Descriptive output names simplify testing and audits.

Steps:

1. Enter the lead scoring expression above. The Hot Lead, Warm Lead and Nurture results will appear automatically. Expression Valid notification should appear.
2. Click “Test Rule” to test the rule.
3. Save the workflow as a draft. Click Save Draft on the top tool bar.

Key editor controls

• Save Draft / Save Changes: Persist changes.
• Test Workflow: Run against a sample payload.
• Version selector: Open and label versions.
• Deploy / Undeploy: Publish or remove a production version.

Testing a Workflow

Permissions

Workflow testing is available to Admins and Editors. Viewers can review previous test results but cannot execute tests.

Testing Steps

1. Select Test Workflow. Located at top tool bar.
2. Provide a lead payload such as the Acme Manufacturing example.

   

3. Run the test.
4. Review the returned score, execution logs, timing, and any errors.

Versions and Publishing

Versions are named snapshots of a workflow. Publishing makes a selected version available via the production endpoint.

Permissions

• Admins can create versions and deploy or undeploy production releases.
• Editors can create and manage versions but cannot deploy them.
• Viewers can review version history only.

Recommended release flow

1. Save the workflow.
2. Test with realistic payloads.
3. Create or select a version, e.g., v1.
4. Add a concise description, e.g., Initial lead scoring rules.
5. Publish/deploy the validated version by clicking Deploy on top tool bar.

Importing and Exporting Workflows

Import brings workflow definitions into the current DecisionFlow organization from either a local workflow folder or a previously exported workflow package.

Export for backups, code review, migration, or promotion between environments. Select one or more workflows and the versions to include.

Importing

Import allows you to bring workflow definitions into DecisionFlow from either:

• A local workflow folder on your computer
• A workflow package previously exported from DecisionFlow

Common use cases include migrating workflows between organizations, restoring exported workflows, or importing workflow definitions from an external source.

Import Methods

Import from Folder:

Use Import from Folder when you have workflow definitions stored in a local directory on your computer.

Select a Decision Rules Engine code base folder containing one or more workflow definitions to import into the current organization.

Import Export Package:

Use Import Export Package when importing workflows that were previously exported from DecisionFlow.

This option is commonly used to:

• Migrate workflows between organizations
• Move workflows between environments
• Restore previously exported workflow packages

Supported formats:

• .json
• .zip

Import Steps

1. Open Dashboard.
2. Select Import Workflows.
3. Choose one of the following:
   • Import from Folder — Import workflow definitions from a Decision Rules Engine code base folder on your computer.
   • Import Export Package — Import workflows previously exported from DecisionFlow.
4. Select the folder or package to import.
5. Review validation messages and any detected issues.
6. Complete the import.
7. Open the imported workflow and run a test before publishing or deploying.

Notes

• Imported workflows are added to the currently selected organization.
• Workflow packages imported through Import Export Package may contain workflows exported from another organization.
• Validation must pass before imported workflows can be tagged or deployed.
• Review imported workflows and execute a test run to verify expected behavior.

Exporting

Export creates a workflow package that can be stored, shared, or imported into another DecisionFlow organization.

Select one or more workflows and choose which versions to include in the export package.

Export Steps

1. Open Dashboard.
2. Select Export Workflows.
3. Select one or more workflows to export.
4. Choose the version(s) to include for each workflow.
5. Select Export.
6. Save the generated export package to your computer.

Notes

• Multiple workflows can be exported in a single package.
• You can export all versions or select specific versions.
• Exported packages can be imported into another DecisionFlow organization using Import Export Package.
• Exporting does not modify the original workflows.

Audit Logs

Audit Logs capture activity for workflows, rules, versions, users, and other tracked actions. Use search and filters (action, entity type, user, date range). Export results to CSV or JSON.

Audit Logs can be viewed by all roles. Permissions determine whether users can only review activity (Viewer) or perform actions that generate audit records (Editor and Admin).

Answer typical questions

• Who changed the scoring expression?
• When was v1 created?
• Who published or unpublished the workflow?
• Was a workflow deleted or imported?

  

Settings

Settings are organized into tabs. Availability depends on your role.

Profile

Update account details such as display name and profile information.

Settings are organized into tabs. Available options depend on your role.

Team

Admins can invite users, manage pending invitations, update roles, and remove members. Add sales-ops users as Editors if they will maintain the lead scoring workflow.

Security

Manage password changes, two-factor authentication, active sessions, session termination, and login history.

Organization Auth Token

Generating Auth Token

RE-generating Auth Token

Settings → Auth Token → Regenerate Auth Token

Persmission Summary

Testing from Postman

1. Copy workflow’s version url

   

2. Paste workflow version url into Postman
3. Set call method to POST
4. Click on Authorization tab and select Auth Type -> Bearer Token
5. Get auth token from Org admin and paste it

   

6. Click on Body tab, select raw and paste request json to test with
7. Click send to get the response

   

Troubleshooting

Best Practices

• Use realistic sample payloads for development and testing.
• Give workflows and rules business-readable names.
• Keep version descriptions short and specific.
• Test with examples for each output category before publishing.
• Review audit logs after high-impact edits or deployments.
• Protect organization auth tokens and rotate when necessary.

Reference: Lead Scoring Walkthrough Summary

1. Create Lead Scoring Workflow on the Dashboard.
2. Add an EXECUTE rule with the JSONata expression.
3. Connect outputs to results: Hot Lead, Warm Lead, Nurture.
4. Test with the Acme Manufacturing payload and verify Hot Lead.
5. Save changes, create version v1, add a description, and publish.