Workflow Sample Reactive - Overview (O11) | OutSystems

Log in

workflow-sample-reactive

Stable version 1.0.0 (Compatible with OutSystems 11)

Uploaded

on 30 June 2020

by

0.0

(0 ratings)

workflow-sample-reactive

Details

A sample application to show how to implement workflow application in Reactive Web. (To use this sample, OutSystems Platform Version 11.8.0 or later is required.)

Asset screenshot_0

Asset screenshot_1

Asset screenshot_2

Read more

To use this sample, OutSystems Platform Version 11.8.0 or later is required.

This sample shows how to implement following functionalities with OutSystems in Reactive Web.

Submit/Re-submit approval requests
Approve/Reject the requests
Show workflow history and process diagram

Note:

Email contents design is not provided for Reactive Web module yet, so sending email feature is not implemented in this sample. If you need email notifications, you can implement it in the Traditional Web and call it from Reactive. (Designing/sending email from Reactive Web will be offered in the future OutSystems version.)

Release notes (1.0.0)

Reviews (0)

Team

Other assets in this category

mobile-utilities

A group of multiple utilities to use on your Mobile or Reactive applications. The main goal is to bring Text, HttpRequestHandler, and other extensions from the server-side to the client-side.

A safe implementation of Stripe (credit card payment processor). More at www.stripe.com

mark-search-text

Component to mark search text in expression

More from Tsuyoshi Kawarasaki

editable-table-reactive-sample

A sample application to show how to implement ‘Editable Table’ in Reactive Web applications.

highcharts-sample-reactive

A sample application to show how to develop custom Highcharts widgets.

column-based-concurrent-update-sample

This forge component shows a sample implementation to achieve column-based concurrent update. This sample shows how we can implement exclusive access control in the following use cases. Scenario 1: User A and B concurrently access the same record of SampleTable. User A modified ‘Name’ field and saved the data. Then, User B modifies ‘Description’ field and saves the data. In this scenario, User B can save his/her data without any warning. Scenario 2: User A and B concurrently access the same record of SampleTable. User A modified ‘Description' field and saved the data. Then, User B modifies ‘Description' field and saves the data. In this scenario, User B gets warning. The warning says "The Description field was already modified. Will you override it with your data?"