Overview of object workflows

The Data feature in Yapla allows you to collect data and process it using validation processes (workflows). Yapla offers two modes of operation: customized workflows and system workflows. There are currently four system workflows: Simple Validation, Submission, Payment, and Validation with Review. For more specific needs, the customized workflow allows you to define your own statuses.

Status changes in each workflow also allow automatic communications to be triggered and documents to be linked to them. You can configure them under Data > Object.

1. Select the desired object and go to the Document tile.
2. Create all the documents you want to link to your communication.
3. Go back to the object in question under the Communication tile.
4. Create your message, link it to the desired status, and attach your document below. (Note that it is important to create your documents before linking them to your communications.)
   

All types of workflows can be linked to a fee. That is, a step can be added to the submission of a form. You will find this optional step represented by dotted lines in the diagrams below.

Select your workflow

Workflows are found in the Settings menu of your object.

In the Workflows submenu you can select the one that suits you.

Type A - Simple validation

This type of workflow is used for simple forms that do not require approval by a Yapla administrator. For example, this workflow can be used for a contact form or a newsletter subscription. 

Status	Description
New	Initial status when a request is created.
Validated	The request has been validated.
Cancelled	The request is cancelled.
Destroyed	The request is destroyed and is not recoverable.
Archived	The request is archived.

Type B - Submission

This type of workflow is used for elements that require the user to submit the form once it has been completed. This workflow will be used when the request is linked to a member by an Object field. This allows members to connect to their Member Space and complete forms that have been assigned to them by a Yapla administrator. For example, this workflow can be used to fill out evaluations, fill out surveys, fill out a self-evaluation request, etc...

 

Status	Description
New	Initial status when creating an item.
In progress	The member is completing the form.
Submitted	The form has been submitted by the member.
Cancelled	The item is cancelled.
Destroyed	The item is destroyed and is not retrievable.
Archived	The item is archived.

 

Type C - Payment

This type of workflow is used for forms that require a payment step. For example, this workflow can be used for a guide purchase form, for the payment of an advertising request, etc. Learn more about adding prices to objects.

 

Status	Description
New	Initial status when a request is created.
Waiting for payment	Status when the selected payment is payment by check or bank transfer.
Transaction Completed	Status when the payment has been completed.
Validated	The request has been validated.
Cancelled	The request is cancelled.
Destroyed	The request is destroyed and is not recoverable.
Archived	The request is archived.

 

Type D - Validation with review

This type of workflow is used for forms that require a Yapla administrator to approve the request. This workflow will be used when the request is linked to a member by an Object field. This allows members to connect to their Member Space and submit requests for approval. It allows Yapla administrators to approve, refuse or request modifications to the request. For example, this workflow can be used to fill in accreditation requests, article publications, etc... It is also possible to associate a payment to this workflow.

 

Status	Description
New	Initial status when creating an element.
Approved	Status when the Item has been approved by an account administrator.
Approved and Pending Payment	Status when the Item has been approved and payment is now pending.
Pending Change	Status when an edit request is pending.
Pending Approval	Status when an item has been sent for approval.
Ready to Submit	Status when the form is completed and ready to be sent for approval.
Rejected	The item is declined by an account administrator.
Rejected and Pending Payment	The item is declined by an account administrator but payment is still required.
Cancelled	The item is cancelled.
Destroyed	The item is destroyed and is not recoverable.
Archived	The item is archived.

 

Type E - Training

This workflow is used when a form is used for training offers. For example, when these training sessions are assigned to trainers and they need to confirm their attendance.
Once the request is accepted, the training provider assigns a trainer to the request. The status changes to "waiting for the trainer." The trainer (member) will receive a communication and, upon logging into their member area, will be able to view the request. The trainer can then modify or complete a section of the form if necessary or decline the request. In this case, the training provider is notified and will return to the first step. Once the training is delivered, the status of the form can be manually changed to: Training delivered.

Status	Description
New	Initial status when an item is created
Pending approval or modification	Status when the item is awaiting approval or modification by the training provider.
Cancelled	Request cancelled by the training provider
Waiting for trainer	Status when the item is awaiting a response from the trainer (chosen hours and date)
Approved by trainer	Status when a request is approved by the trainer
Declined by trainer	Status when a request is declined by the trainer
Training delivered	Status when the training has been completed

 

Type F - Customized workflow 

This workflow allows the Yapla administrator to manually associate the status of an element but it also allows him to create his own statuses. Here are the basic statuses that are present when an object is created: 

Status	Description	Yapla Administrator
New	Initial status when creating a request.	The Yapla administrator can select any status at any time. The status change is done directly on the form.
Validated	The request has been validated.
Cancelled	The request is cancelled.
Destroyed	The request is destroyed and is not recoverable.
Archived	The request is archived.

At each status change, a customized communication can be sent by email automatically. For example, it is possible to announce to the person who filled the request that it has been received and will be validated shortly.

How do I refund a payment made with the object application?

Note that no refund option is currently offered on payments linked to data workflows.