# Example workflow (Example Model Based Form Binding Identity Create and Update) not showing confirmation messages

**URL:** <https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq, identity-processing, workflows\
**Created:** [March 4, 2025, 3:24am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033 "2025-03-04T03:24:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![anloh](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@anloh](https://developer.sailpoint.com/discuss/u/anloh)\
**Post date:** [March 4, 2025, 3:24am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/1 "2025-03-04T03:24:04Z")

</div>

## Which IIQ version are you inquiring about?

8.4p1

## Share all details about your problem, including any error messages you may have received.

I have imported this workflow tagged to a custom quicklink along with the form for Example Model Binding Identity Create and Update Form. After creation of the identity or edit identity, there is no confirmation message presented to the user in the UI that shows that it has been successfully generated. Example : Request submitted successfully. The ID for this request is 2423 // Identity attributes change submitted // Created identity request submitted. Am I missing something in the workflow?

Thank you.

---

<div class="post-metadata">

**Author:** ![ryan\_toornburg](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ryan_toornburg/32/21550_2.png) [@ryan\_toornburg](https://developer.sailpoint.com/discuss/u/ryan_toornburg)\
**Post date:** [March 4, 2025, 12:07pm UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/2 "2025-03-04T12:07:23Z")

</div>

Hi @anloh - On your quicklink definition make sure you have something like this: `<entry key="workflowSuccess " value="Request Submitted Successfully"/>`

---

<div class="post-metadata">

**Author:** ![anloh](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@anloh](https://developer.sailpoint.com/discuss/u/anloh)\
**Post date:** [March 5, 2025, 6:24am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/3 "2025-03-05T06:24:43Z")

</div>

This worked thank you! If I were to include failures what would the syntax be like and to include the requestID in the quicklink would that be possible?

---

<div class="post-metadata">

**Author:** ![anloh](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@anloh](https://developer.sailpoint.com/discuss/u/anloh)\
**Post date:** [March 5, 2025, 7:08am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/4 "2025-03-05T07:08:27Z")

</div>

I just read further into the quicklink documentation :

**NOTE** : The Quicklink is only aware of the workflow launch, not its execution status, so this message is for indicating the workflow started successfully, not that it completed successfully. Typically, this is only used when the workflow does not include any UI pages for user interaction but just launches an operation in the background.

For the example workflow & form, even if the user does not submit the form, when the user cancels, it still shows this. Is there anyway we can interject the message to only show once it is submitted successfully?

---

<div class="post-metadata">

**Author:** ![kalyan\_dev32](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kalyan_dev32/32/21870_2.png) [@kalyan\_dev32](https://developer.sailpoint.com/discuss/u/kalyan_dev32)\
**Post date:** [March 5, 2025, 7:17am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/5 "2025-03-05T07:17:27Z")

</div>

Check these posts:

- [Triggering a Workflow via QuickLink](https://community.sailpoint.com/t5/IdentityIQ-Forum/How-to-trigger-a-workflow-via-quicklink/m-p/265245): Use action=“workflow” and set workflowName in the QuickLink Attributes.
- [httpSession Null Issue](https://community.sailpoint.com/t5/IdentityIQ-Forum/Getting-httpSession-as-null-in-workflow/m-p/230794/highlight/true#M175952): Pass data via attributes instead of relying on httpSession.

---

<div class="post-metadata">

**Author:** ![kalyan\_dev32](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kalyan_dev32/32/21870_2.png) [@kalyan\_dev32](https://developer.sailpoint.com/discuss/u/kalyan_dev32)\
**Post date:** [March 7, 2025, 7:15am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/6 "2025-03-07T07:15:20Z")

</div>

> [@anloh](#):
>
> Is there anyway we can interject the message to only show once it is submitted successfully?

Yes, it’s possible. check this post [Display success message - #7 by kalyan\_dev32](https://developer.sailpoint.com/discuss/t/display-success-message/103162/7)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [May 6, 2025, 7:16am UTC](https://developer.sailpoint.com/discuss/t/example-workflow-example-model-based-form-binding-identity-create-and-update-not-showing-confirmation-messages/103033/7 "2025-05-06T07:16:04Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
