Position

The position object represents the user action steps that take place in the flow.

An action by the system is expected from the end user defined in each position object placed in the flow design. Basically, this object is used to submit a business process to the approval of the person. By default, the system sends a confirmation mail to the relevant end user for each "Position" object placed on the flow design, and also ensures that this business process is placed in the user's "Approvals" list in the Web interface.

The contents of a position object can be given statically at design time or changed dynamically by various methods. The most common of these methods is to use the "Assignment"** object. With the help of this object, the user involved in the corresponding business process step can be dynamically discovered, and the content can be changed during the flow. The position object can also be assigned to the user or position-based person with the code.

When the object in the Flow design screen is clicked, the object properties appear in the Property Viewer panel.

When the position object is clicked, there are "Appearance", "Properties" and "Events" tabs in the Property Viewer panel.

Appearance

Text Configs

'Object Name' - The name of the object to be used on the system side. On the code side, the object is accessed by the value that is written in the object name field.

'Caption' - The area where the object's title text is entered.

'Is Lock' - This field is activated if the object is not to be moved at the time of design.

'Size' - The part where the width and height of the object are adjusted.

Properties

Value

'Type' - This field determines which user or position the position object will represent. Depending on the assignment type selected from the Type field, the lists of values that will be defined to the Position object will change.

• Type:Fixed position selection; The position object is used to select a position record defined in the system. When the flow reaches this Position object, the approval request will be dropped to the user with the selected position record. When the "Fixed Position" value is selected in the Type field, all position records defined in the system are listed in the "Value" field. The position definition selected from the Value field is set to the Position object, and this Position object now represents the corresponding position.
• Type:Fixed user selection; The Position object is used to select a user record defined in the system. When the flow reaches this Position object, the approval request will be dropped to the selected user. When the "Fixed User" value is selected in the Type field, the "Value" field lists all the user records defined in the system. The user definition selected from the Value field is set to the Position object, and this Position object now represents the corresponding user.
• Type:Stream initiator selection; It is used to assign the user who started the flow to the Position object. Whoever initiated the flow is automatically assigned to the position object. When the stream reaches this Position object, the assertion is dropped to the user who initiated the flow.

Message

'Send Mail' - When the flow step falls on the corresponding Position object, the system automatically sends an e-mail to the person in the object informing them that a process has been dropped for approval. If mail is not requested to be sent when action drops on the corresponding object, the Send Mail field can be unchecked. This is typically used to avoid sending mail to people in test flow scenario trials.

TIP

In addition to turning off email sending by navigating through objects, it is also possible to block email sending across the flow. Email sending can be turned off across the flow by activating the Disable Email Sending feature in Flow Properties>-General.

'Caption' - The header of the confirmation mail to be sent to the user in the position object. The header information includes the "ProcessCaption", "FirstName", and "LastName" parameters that come by default. These parameters are the system's own parameters and the title of the process to which the mail is sent, the name and surname of the person to whom the mail is sent are automatically filled in by the system. The mail header structure that comes by default is as follows. The developer can change the title of this mail if he wishes.

> Bimser Synergy {{ProcessCaption}} confirmation ({{FirstName}} {{LastName}})

'Message' - The message text part of the mail to be sent to the position is located in this field. By default, the incoming message text can be changed optionally.

'Attachments' - If you want to send an attachment file in the mail to be sent to the position, it is defined from this field.

Clicking on the Atttachments field opens the screen where it will be defined to select the type of attachment that is desired to be added to the e-mail to be sent.

In the Attachments edit window, the **"Insert" button can be used to define the attachment for adding an attachment to the e-mail to be sent to the contact in the Position object, change the attachment settings by clicking on the line in the made definition, or press the trash can icon that appears in the details of the attachment line and remove the event from the object.

• The Type field is the field where the attachment file is located. DM, Flow, RelatedDocuments can be selected.
  • Selecting Type:DM makes the selection in Document Management within the Value field in the panel.
  • When Type:Flow is selected, the object containing the Id of the file to be added as an attachment can be selected as liquid or static data can be written. ({{ Document1.DocumentId }}, {{ Variable1.Value }}, 56669)
  • When Type:RelatedDocuments is selected, the Document field appears to select the Document object containing the form containing the RelatedDocuments object to use. Selecting indicates that the Related Documents field appears in the panel and lists the Related Documents objects within the selected object.

'Edit Message Source' - This feature is activated if the message to be sent to the contact in the position object is intended to be sent as a customized message template and not as the system default. When the feature is activated, the area named "Source Message" will be visible.

'Source Message' - The screen that allows the default mail template to be displayed in html format and modified is opened from this area. The designed mail template can be viewed instantly in the preview window.

If you want to edit a certain language in the e-mail, the language option in the panel can be changed and the e-mail codes and preview of the selected language can be made.

INFO

The language in which users receive e-mail in the system is determined by the selection made in the Default Language field in each user in the Human Resources section.

<div style={{textAlign: 'center'}}>

</div>

Push Notification

CAUTION

Push Notification is sent via the mobile application to the devices of the person/persons who have logged in to the Bimser Synergy CSP application and have given permission to the notifications.

'Send Push Notification' - If you want to send a notification on the mobile device of the person in the position object, the field is activated.

'Caption' - The header information of the mobile notification to be sent to the person in the position object. The header information includes the "ProcessCaption", "FirstName", and "LastName" parameters that come by default. These parameters are the system's own parameters and the title of the process to which the information is sent, the name and surname of the person to whom the e-mail is sent are automatically filled in by the system. The mail header structure that comes by default is as follows. The developer can change the title of this mail if he wishes.

> Bimser Synergy {{ProcessCaption}} confirmation ({{FirstName}} {{LastName}})

'Message' - The text part of the informative message to be sent to the person in the position object is located in this field. By default, the incoming message text can be changed optionally.

Documents

'Documents' - This field sets which form and which view of the form the user in the position object can see. The forms included in the project are kept in the Document object on the flow side. The document object represents the form that is linked to it and the data on the form. A flow can have multiple, different Document objects that represent different forms. If the user in the position object is asked to see which form, from this field the Document object to which the corresponding form is linked is selected and the necessary settings are determined.

More than one Document object can also be added to the user defined in the Position object for the user to see in the web interface. When clicking on the Documents section, one or more Document objects that the user wants to see are added with the "Insert" button and the settings of the edits that can be made on the document are determined.

Properties tab properties

Feature	Description
Document	The area on the flow design where all Document objects are listed. The Document object to which the form that is intended to be shown to the person in the position object is linked is selected from this field.
View	The views of the form to which the Document object selected from the "Document" field is linked are listed in this field. When the user in the position opens the form, the form view that he is asked to see should be selected from this field. If no selection is made from the view area, the user will see the "default" view.
Panel Size	It is the area that determines the width at which the document object defined in the web interface can be opened. Selecting one of the 1-2-3 values will open the panel size at the selected value width.
Editable	This field determines whether the user in the position object can edit the document. A document without the Edit field checked opens to the user in read-only mode in the web interface, and the contact can't edit the form. If editing is desired on the form, this field must be checked.
Show events	This is the area where the user in that step is set to see event buttons on the form that they will take action to advance the form and continue the flow. If the user needs to use the action buttons to act on the relevant document and include it in a workflow, this field should be checked. If the document is attached to the user for informational purposes, the action event buttons do not need to appear in this document and in this case the "Show events" field should not be checked.
Signature	The system supports digital signature infrastructure. If certificates have been obtained from digital signature providers, this option can be used for signed approvals of workflows and documents.The signature field lists 4 options;<br/> No sign : Selected<br/> to indicate that no digital signature will be used on the document Optional : Optionally selected when using a digital signature on the document. When the process comes to the user in question, it is up to the user whether the document is digitally signed or not.<br/> Required : Requires the user to sign the document with a digital signature certificate, regardless of whether they have a certificate or not.<br/> Required if possible : If a digital signing certificate exists for the user, the system forces the user to use the digital signing certificate to approve the document. The requirement applies to the user only if a specific certificate exists.

Signature tab properties

This is the part where detailed edits to the document signing settings are made.

Feature	Description
Signature	An area that determines whether the document is signed using CAdES or PAdES types.
Timestamp	It is the feature that is activated when you want to use the time denga when signing the document.

:::d anger WARNING

If the document object inserted within the object has a signature set, the document object to be signed must contain documents (pdf etc.) and signatures must be placed on the documents. CSP forms cannot be signed!

:::

CAUTION

If the signature setting has been made on the document object inserted within the object, the Digital Signature Required selection in the event must be activated in the event in which the signature operation will be performed in the Events section of the same object attached in order for the signature process to be initiated in the web interface.

Events

'Events' - This is the part of the position object that defines the action events that the user can take for the form in the web interface. The events defined in this field appear as action buttons on the form in the web interface. Whichever event button the user clicks, the process proceeds to the flow step where the connection arrow for that event is connected at the moment of design.

If the number of events has been added to the object from the Events area, the connection arrows to represent each event must be extracted from the object in the flow design screen, and these arrows must be connected to wherever the stream is intended to go when the corresponding event is clicked.

Clicking on the Events field will open a window where events to be added to the object can be selected and edits can be made for those events. Here the events defined in the Flow Properties->Events tab are listed as event records. By default, the Position object has the "Confirm" and "Reject"** events attached. To modify existing events, add a new event, or remove an existing event from the object, clicking the Events field opens the event editing window.

A new event can be added to the Position object with the **"Add" button in the Events editing window, the event settings can be changed by clicking on the event line for attached events, or the event can be removed from the object by pressing the trash can icon that appears in the attached event line details.

Feature	Description
Identity	The id value that represents the event appears in this section. This field is in read-only mode and cannot be changed.
Description	The area where the text portion of the event appears.
Visible	This feature must be activated in order for the corresponding event button to appear in the web interface.
Validate	In order to work with the mandatory conditions given in the object properties at the time of form design and the controls written in the validation Rule Manager section of the form, and to give a warning message to the user in cases where the desired condition is not met or the mandatory objects are left empty, the "Validate" field must be checked on the event button clicked by the user.
Reason	When an event with a reason field marked is clicked on in the web interface, a field is removed for the user to enter a description of the reason. It is typically used for the Reject event, and when the person wants to reject the form by pressing the Reject button, they are prompted to enter the reason for the rejection in the reason field.
Reason Title	The field where the reason description is shown in the web interface is the field where the expression in the header is customized.
Digital Signature Required	Clicking on an event in the web interface with the digital signature required field marked will open the screen required for the user to perform the E-signature process. For the signing process to begin, the Signature settings must be set on the document object defined in the object.
Form	From the form field, all the Document objects that are in the flow are listed. When a Document object is selected from this field for any event, clicking on this event in the web interface opens the screen of the defined form within the Document object selected from the Form field in front of the user and the user is expected to fill in the fields in the form. When the user fills out the form that opens and says OK, the flow proceeds to the next step. This completed form becomes the "Event Form" of the corresponding flow object.
Icon	The icons of the event buttons that will appear on the form in the web interface are selected from this area. By default, the icons of the incoming events in the system are automatically specified in the icon column.

CAUTION

If the settings for an event that was added to the object context were changed in Flow Properties->Events, the attached event record in the object context might not be affected by this change. After the change, objects that use the corresponding event may need to be checked and the event for which the change was made may need to be removed and re-added from the Events area.

CAUTION

If an event attached to an object is deleted from the Flow Properties->Events area, the corresponding attached event record within the object must also be deleted, checking for objects that use that event.

Options

'Hide the Approver' - Feature that allows you to show the name of the user in the position in the flow history as hidden as * * * *.

'Show in the Flow History' - This is where it is set whether the corresponding flow step is shown in the flow history or not.

Flow Control

'If Processed Before Do Not Send Request' - According to the flow scenario, in some cases the stream may be resent to a person who is transacting. In such cases, it may be desirable to continue the process without the user having to take action again.

To illustrate the situation with an example, in a designed Workflow, the user is asked to go to the approval of the HR manager after the approval of the manager. In such a scenario, when a staff member from the HR department starts the business process, the HR manager will already approve the process as the manager, so the document will come to him again and he will have to approve the same document a second time. In order to avoid such scenarios, the "If Processed Before Do Not Send Request" option is used.

When the "If Processed Before Do Not Send Request" option is activated, the new control fields "Before Processed Events" and "If Document(s) is/are Changed Then Request is Needed" will be visible.

'Before Processed Events' - If the user has already consented with one of the events defined on the field, it allows the process to be automatically confirmed by selecting the relevant event in the field.

For example, in a designed Workflow, the user is asked to go to the HR manager approval after the manager approval, and both objects have the "Approve Permission Request" event. In such a scenario, when a staff member from the HR department starts the business process, the document will come to him again as the HR manager will approve the process. However, the process will continue automatically because the "Approve Permission Request" event is attached to the field and the HR manager has already given approval using this event beforehand.

TIP

If Processed Before Do Not Send Request and Before Processed Events work if the user has previously used the process-defined event.

CAUTION

Once the If Processed Before Do Not Send Request feature is executed, code can be written at the API level (by accessing the object property in the stream) to reactivate it.

'If Document(s) is/are Changed Then Request is Needed' - Let's elaborate a little more on our previous scenario and assume that there is another position approval between the manager approval and the HR manager approval. When the HR staff fills out the document, it will first go to the manager – where the manager becomes the HR manager – and then to the approval of the other Position involved in the work process. After the other position approval, the process will be completed without visiting the HR manager again due to the "If Processed Before Do Not Send Request" option. However, if the Position object in our scenario has made any changes to the document, that is, if the document has become different from the initial approval of the HR manager, the process will be completed before the HR manager sees this document a second time. As a second option to eliminate such situations, the "If Document(s) is/are Changed Then Request is Needed" option has been added to the system. Thus, using this option, the relevant document can be made to go back to the HR manager in the scenario described above.

Forwarding Options

'Enabled' - The process sent to the user in the position object is used by the user to route the process to the people who are added to the Members field in the flow design. When the feature is active, the Forwarding event appears next to the Event buttons on the web interface for routing.

For example, let's assume that in a Purchase process, the user's approval comes to the process and the Forwarding option is active. When the user examines the process content, he should realize that it is not about himself, that X person in the same department should do this job. Instead of sending the process back to the user who started the flow and selecting the right person or contacting the system administrator to fix it; By clicking on the Forwarding event, the process is sent to the selected user to take action.

CAUTION

In the forwarding process, the person to whom the approval is directed cannot send the process to a different person again. If it is requested to be sent to a different person, the process must be sent back to the user who made the redirect and the user must repeat the forwarding process.

'Members' - This field defines the users who will route to the Position object. Clicking on the field will open a screen with a "Contents" button to select the contacts to be added to Forwarding and a "Delete" button to remove the added records.

Pressing the "Contents" button will open the selection area where it will be indicated which type of content to add. Area; There are 3 options listed as Position, Position groups and Object on document.

{#members-position} if position selection is made

When the position option is selected, a new pop-up will open and in this field; The Fixed Position, User, Variable Position, and Flow Initiator options are listed.

• When the fixed position option is selected, the screen will list all the position records available in the system. When one or more position records are selected from this list and the "Create" button is pressed, the selected position records are added to the Members area. If the developer wishes, he can continue to fill in the field content by pressing the "Contents" button again.

• When the user option is selected, the screen will list all the user records present in the system. When one or more user records are selected from this list and the "Create" button is pressed, the selected users are added to the Members field. If the developer wishes, they can continue to fill in the group content by pressing the "Contents" button again.

• When the variable position option is selected, the screen lists all the Position objects and the Flow Initiator object that are present in the flow design. If the person or position in the flow is desired to be added into the Members field, the Position objects representing that person or position are selected from this field. After pressing the "Create" button, the developer can continue to fill in the group content by pressing the "Contents" button again if he wishes.

• Selecting the Flow Initiator option adds the user who started the flow in the Members field. If the developer wishes, they can continue to fill in the group content by pressing the "Contents" button again.

{#members-position-groups} if selecting position groups

When the Position Groups option is selected in the Members area, a new pop-up opens and in this field; The options Document approvers/rejectionists, User group by title, User group by department, and User groups are listed.

• The document approvers/rejectionists option is the option used in the corresponding flow design to add whoever took action until the flow reached the Position object to the Members field. If the developer wishes, they can continue to fill in the group content by pressing the "Contents" button again.

• The User group by title option is the option used to add users with a specific title definition to the Members field. Selecting this option from the "Contents" area lists all the title records defined in the system.

According to the selection made in the screenshot below, it means that users with the title "Project Manager" will be added. If the developer wishes, they can continue to fill in the group content by pressing the "Contents" button again.

• The User group by department option is the option used to add users who are in a specific business unit. Selecting this option from the "Contents" area lists all the department records defined in the system.

According to the selection made in the screenshot below, it means that the users in the "Product Management" department will be added to the Members field. If the developer wishes, they can continue to fill in the group content by pressing the "Contents" button again.

• When the user groups option is selected, the screen will list the User Groups defined under the Human Resources heading in the user interface. When the developer selects a user group from this list, the users defined in the Members field are added to the selected user group. When new users are added to or removed from the relevant user group from the Human Resources section, the flow appears in the Forwording list of the contacts in the last updated version of the user group in the Members field where this user group is selected.

{#members-documents} if the object selection on the document is made

• Used to add users or positions selected in a DataGrid object on the form to the Members area when the On-document object option is selected. The process of adding people in the field can be made position-based or user-based.

If the contacts selected in the DataGrid object on the form are to be added to the field on a per-user basis, the table objects must have an ID column that contains the "User Name (registration number)".

If the people selected in the DataGrid object on the form are to be added to the field based on position, the table objects must have an ID column that contains the "Position id" information.

When the "Object on document" option is selected from the Contents area, the following fields will appear on the screen;

Feature	Description
Document	This area lists all the Document objects that are included in the flow design. If the data of the DataGrid object on the form is intended to be accessed, the Document object in which that form is defined is selected from this field.
Data type	The "User" and "Position" options will be listed. If the records to be added to the Members field are to be added on a per-user basis, "User" should be selected from this field, and if they will be added on a position-based basis, the "Position" option should be selected from this field.
Table / Details	Whichever DataGrid object on the form is inserted in the Documents field, the selected contacts are selected in the Members field.
Field	This area lists the columns of the DataGrid object. If "User" is selected as the data type, the column containing the user IDs should be selected in this field. If "Position" is selected as the data type, the column containing the position IDs should be selected in this field.

'Use Referred User As Actual Value' - This is the property that determines that when the Position object where the Forwarding feature is active is selected as the source in the Assignment etc. objects in the flow design, the person information to which the process is directed is used on the flow from now on.

Time Out

This section uses it to add a time-out action to the position object. When the flow falls on the position object, within a certain period of time, if the person in the position has not taken any action, the request times out and it is desired from anywhere in the flow to continue the operation, the parts contained in this section are filled. If the fields in the Timeout section are full and the "Timeout" link has been removed from the Position object, the request times out at the end of the specified time and the flow proceeds from where the "Timeout" lever is connected.

'Day' - If the expected action from the position is to time out at the end of a certain day, the timeout day information is written in this field.

'Hour' - If the expected action from the position is to time out at the end of a certain hour, the timeout time information is written in this field.

'Minute' - If the expected action from the position is requested to time out after a certain minute, the timeout minute information is written in this field.

'Calculate Using Working Hours' - This field is checked to run the timeout period by calculating the working hours defined in the system.

'Calculate Using Holidays' - This field is checked to run the timeout period by calculating the holidays defined in the system.

INFO

It is checked by the system that the attached properties on the object are correct. When a missing feature is found, a red exclamation point icon can be displayed on the object, and hovering over the icon with the mouse pointer can display what is missing or incorrect.

Events

The events owned by the position object are located in the "Events" tab in the Property Viewer panel. Each event is triggered at different runtime moments, performing its own unique operations. Code written by the developer to these events is also executed at the time the corresponding event is triggered. To write code for any event, double-click the appropriate event line from the Events tab. The screen is directed to the flow code editor section named "FlowName.cs" and the method block for the clicked event is automatically created. The developer can construct any code block he wants in this method. Next to the event whose method is created on the code side by clicking from the Events tab, the method name information is automatically generated and the relationship between the event and the method is specified.