Disclosure
An information object is an object used to send an information mail to the people defined in the system at any time in the process.
The notification object is generally used to send an information e-mail to users who have passed through the process or to users who need to be informed about the process.
The contents of the informational object can be statically defined or populated with code.
When the object in the Flow design screen is clicked, the object properties appear in the Property Viewer panel.
When the information 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
Group Content
'Group Content' - The content of the Information object is filled in to select the person or people to whom the notification mail will go from this field. Clicking on the group content area will open a screen with the "Contents" button to select the contacts to be added to the Notification object, the "Create" button to create the selected contacts in the object, and the "Delete" button to remove the added records from the group.
Pressing the "Contents" button will open the selection area, where it will be indicated which type of content to include in the Information object. 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. Selecting one or more position records from this list and pressing the "Create" button adds the selected position records to the Information object. 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. Selecting one or more user records from this list and pressing the "Create" button adds the selected users to the Notification object. 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 to the information object, the selection of Position objects representing that person or position is made 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 Stream Initiator option adds the user who initiated the flow to the Notification object. 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 Group Content field in the information object, 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 came to the Notification object. 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 Info object. 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 business unit option is the option used to add users in a specific business unit to the Notification object. Selecting this option from the "Contents" area lists all the department records defined in the system.
According to the selection made in the following screenshot, it means that the users in the "Product Management" department will be added to the Information object. 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 within the selected user group are added to the Infologi object. When new users are added to or removed from the relevant user group from the Human Resources section, the flow to the Information object from which this user group is selected is notified to the people in the user group in its last updated form.
{#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 Information object 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 information object are to be added on a per-user basis, "User" option should be selected from this field, and "Position" option should be selected from this field if it is to be added on a position-based basis. |
| Table / Details | If the people selected from which DataGrid object on the form inserted in the Documents field will be added to the Informational object, the corresponding object is selected. |
| 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. |
Documents
'Documents' - This field sets which form and which view of the form the user in the Disclosure 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 information object is asked to see which form, the Document object to which the relevant form is linked is selected from this field and the necessary settings are determined.
Clicking on the Docs section lists all the Doc objects available on the stream.
More than one Document object can also be added to the user defined in the Notification object 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 to be shown to the person in the information 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 notification 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. |
Message
'Send Mail' - When the flow step falls on the relevant Notification object, the system automatically sends an e-mail to the person in the object informing them that a process has been reduced to their information. If the object does not want to send an information mail, 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 information of the information e-mail to be sent to the users in the information 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 e-mail to be sent to the users in the notification object 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 users in the information object, 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 editing window, the **"Add" button can be used to define the attachment to add an attachment to the e-mail to be sent to the person in the Information object, the attachment settings can be changed by clicking on the line in the made definition, or the event can be removed from the object by pressing the trash can icon that appears in the details of the attachment line.
- 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 contacts in the notification 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 notifications on the mobile device of the people in the notification object, the field is activated.
'Caption' - The header information of the mobile notification to be sent to the contacts in the notification 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 notification object is located in this field. By default, the incoming message text can be changed optionally.
Action
'Continue If Error Occurs' - When the feature is activated, the ContinueIfErrorOccured connection arrow is used in addition to the Continue link arrow of the Notification object. When the assignment process cannot be done due to incorrect design in the object, lack of assignment information, etc., the process can proceed through this arrow instead of giving an error on the end user side, and the process can be made to perform a different operation when an error occurs.
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 informational 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.