YoutrustUser action with decisionStable

Sign document in Journey (Youtrust)

Presents a Youtrust signing session directly in the Ormuz User Journey for one signatory, then routes the process as soon as Youtrust confirms a terminal result.

Nom de la demande

Documents

Contact Ormuz

Faire signer un document dans le parcours (Youtrust)

Signé

Refusé

Expiré

Annulé

Signature request Youtrust

Documents

Vue d’ensemble

Have a document signed in the journey (Youtrust) keeps the signatory in the Ormuz experience: the Youtrust signing page is embedded, then the process automatically resumes when the request is signed or declined.

This node is intended for the person currently present in the journey and accepts exactly one contact as signatory.

The process resumes when Youtrust confirms signature or decline.
The domain displaying the experience must be allowed in Youtrust iFraming settings.
The same Smart Anchors as for email signature define document fields.

Typical scenario

At the end of onboarding, the representative immediately signs the mandate displayed in the journey. The signed route then continues case activation.

Quick start

First enable iFraming in Youtrust, then bind a document containing a Smart Anchor and the contact currently participating in the journey.

Compte Youtrust

iFraming enabled
https://journey.ormuz.io/ added to allowed domains
Sandbox or production configuration consistent with the account

Request

Exactly one signer
PDF or DOCX with an s1 anchor
Simple or advanced level compatible with the iframe

Configuration example

Parameter	Binding	Role
`documents`	`contract_file`	Document containing an `s1` anchor
`signer`	`current_contact`	Person present in the journey

Attention Mandatory prerequisite: in Youtrust iFraming settings, explicitly allow the https://journey.ormuz.io/ domain before production use.

Decision routes

signed

Request signed

All expected signatories signed and Youtrust considers the request complete.

Recommended actionContinue the business process and use signed documents or audit trails as needed.

declined

Signature declined

The signatory declined to sign the request.

Recommended actionStop handling that requires a signature and plan the appropriate communication or business review.

expired

Request expired

The deadline was reached before all expected signatures were obtained.

Recommended actionDecide whether a new request should be created with a new expiration date.

cancelled

Request canceled

The Youtrust request was canceled before completion.

Recommended actionStop automatic continuation or create a new request if cancellation does not end the business need.

Key point A non-terminal request selects no route: the process remains waiting for the Youtrust result.

Process example

Contract to sign

Faire signer un document dans le parcours (Youtrust)

Signé

Refusé

Expiré

Annulé

Poursuivre

Handle the decline

Relancer

Present signing to the contact in the Ormuz experience and automatically resume on the corresponding Youtrust route.

Data resolution

The node builds the request from linked Ormuz objects.

Data	Source or rule
Signatory identity	First name, last name, and email from the `contact` supplied in `signer`.
Champ `s1`	Location of the single signatory's Smart Anchor in the document.
Delivery channel	Signing session presented in the Ormuz experience.
Journey completion	Terminal event emitted by the Youtrust interface after signature or decline.

Parameters 13

Request and documents

Configuration, name, and documents defining the request.

extension_config_idRequisref(extension_config:youtrust)

Active Youtrust configuration used to create or retrieve the request. It notably determines sandbox/production environment and default language.

nameRequisstring

Business name of the signature request, visible in Youtrust. Choose a title that clearly identifies the contract or case.

documentsRequisFile

An Ormuz file or list of PDF/DOCX files to sign. Signature locations must be defined in the documents using Youtrust Smart Anchors.

Signatories and security

Recipients, order, signature level, and authentication.

signerRequisContact

Ormuz contact signing in the embedded experience. This node accepts exactly one signatory so the user action corresponds to the person present in the journey.

signature_levelOptionnelenum

Requested signature level: simple by default or advanced. Verify that your account and selected authentication mode support the requested level.

authentication_modeOptionnelenum

Signatory authentication mode: no_otp, email_otp, or sms_otp. SMS mode requires a usable phone number to be available to Youtrust.

Lifecycle and retention

Deadline, business reference, and proof retention.

expiration_dateOptionneldate

Request deadline as a date. After this date, an incomplete request may take the expired route.

external_referenceOptionnelstring

Optional business reference sent to Youtrust to make reconciliation with your contract or case easier.

persist_artifactsOptionnelboolean

When enabled, Ormuz retains final signed documents and audit trails as platform files when Youtrust makes them available.

Journey resumption

Advanced settings governing replay of the user action.

allow_replay_from_hereOptionnelboolean

Allows an authorized operator to resume the process later from this user action. Enable only when presenting the same request again is acceptable.

replay_boundaryOptionnelboolean

Marks this signature as a replay point of no return. This prevents unintentionally replaying steps that created or sent the request.

Other parameters

titleOptionnelstring

Title displayed to the signatory in the embedded experience before and during signature. It should clearly identify the document or expected action.

descriptionOptionnelstring

Supporting text shown to the signatory in the embedded experience to explain context and business consequences of signing.

Outputs 9

Youtrust request

Request, documents, and people tracked at Youtrust.

signature_requestYoutrust signature request

Youtrust request with identifier, current state, and available signature-lifecycle information.

documentsYoutrust document[]

Youtrust documents attached to the request, including available identifiers and metadata.

signerYoutrust signer

Youtrust signatory shown in the embedded experience.

Decision

Result used to continue or route the process.

signature_resultOptionnelYoutrust signature result

Business result of the request, notably its state and signed, declined, expired, or cancelled decision.

selected_routeenum

Terminal route selected by the node: signed, declined, expired, or cancelled.

selected_valueenum

Decision value that led to process routing.

Documents finaux

Evidence and files available at the end of the lifecycle.

audit_trailsOptionnelYoutrust audit trail[]

Youtrust audit trails available for signatories of the completed request.

signed_documents_fileOptionnelFile

Ormuz file containing signed documents downloaded from Youtrust. Available when the request is signed and artifact retention is enabled.

audit_trails_fileOptionnelFile

Ormuz file containing audit trails downloaded from Youtrust when retention is enabled.

Behavior

Prepare the request

The document is analyzed, the single signatory is added, and the request is activated for embedded presentation.

Display signing

The Youtrust signing page opens inside the Ormuz experience authorized by the iFraming allowlist.

Let the signatory act

The signatory reviews the document, completes required authentication, and signs or declines in Youtrust.

Detect completion

The experience ends automatically only when Youtrust emits a signature-completed or decline event.

Route the process

Available artifacts are retrieved, then the corresponding terminal route resumes the process.

Limits and responsibilities

The node accepts one signatory. For several remote people, use the email-signature node or several steps appropriate to the business journey.
Qualified signature is not available in a Youtrust iframe; use a channel supported by Youtrust for that level.
A Youtrust Owner or Admin must authorize the domain used by the Ormuz experience.

Troubleshooting

The signing area remains blank

Check that iFraming is enabled and https://journey.ormuz.io/ appears exactly in the account's allowed domains.

No signature field

Check that the document contains a detectable {{s1|signature|85|37}} anchor and that its text remains on one line.

Signing is complete but the process still waits

Check request events in Youtrust and the webhook configuration of the Youtrust connection.

Smart Anchors and iFraming

Smart Anchors are text markers placed directly in the PDF or DOCX. Youtrust creates each signature field at the marker's location.

Attention Minimal example: {{s1|signature|85|37}} creates an 85 × 37 px signature field for the first signatory.

Segment	Signification
`s1`	Single signatory supplied in `signer`.
`signature`	Field type created by Youtrust.
`85`	Field width in pixels.
`37`	Field height in pixels.

Write each anchor on one line and keep all its segments in the same text block.
Prefer Arial between 10 and 14 px; set the text color to the background color so it remains invisible in the final document.
Every signatory index must exist in the request. An s2 anchor creates no field when only one signatory is supplied.
The node automatically enables anchor analysis and rejects preparation when no anchor is detected in signable documents.

See the Youtrust Smart Anchors documentation for other field types and advanced variants.

Attention In Youtrust, choose “allowed domains only” mode and add https://journey.ormuz.io/ to the iFraming allowlist.

See the Youtrust iframe security settings and iframe integration guide.