You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
Views are different forms of the same table.
SimpleOne supports multiple views which are useful not only for dealing with different sets of fields on the agent interface but also for different platform sections such as the agent interface itself and the Self-Service Portal (SSP). Let us demonstrate this functionality on the incident example.
Incidents have the following views:
- SP View Only – the view is used on the SSP in the My Tickets page for displaying information about incidents created by the current user.
- SP – the view is used on the SPP in the My Tasks page to display information about an incident record. This card contains a Read Only Form widget.
- Service Catalog – the view is used on the SSP for submitting an incident from the Main page (the Create Incident card).
- Service Portal Form
- Default – the view is used on the agent interface (the basic view displaying most of the fields).
- Preview – reserved for the record preview form.
? как добавить вью к новой сущности (название вью то же, сущность другая, eg crm deal, а используем SP или что-то подобное)
Create a new form view
To create a separate view, please complete the steps below:
- On the record form, enter the hamburger menu
and select Configure → Form → Layout.
- In the Form view and section area, click Add new next to the View name field.
- In the modal window appeared, enter the desired view name and click Create.
- Configure the fields to display by moving them from the Available to Selected layout area.
- (Optional) Use the Section option to add more form sections if you need.
- Click Save to apply changes and leave the configure menu.
If you leave the configure menu without clicking the Save button, then the pop-up window will appear. Click OK to save changes or click Cancel to discard them.
Configuring Preview form view
Please note that the Preview view name is reserved for the record preview form displaying in reference fields and info thingy. This form looks like this:
Role required: admin.
To configure a preview form view, please complete the steps below (you need to have admin privileges to perform this):
- Navigate to a table form you need to add a preview form.
- Add a new form view as described in the Create a new view section and give it the Preview name.
- Fill it with desirable fields and click Save.
- After that, when clicking on a record in a referenced field related to this table, you will see a preview form containing brief information about the referenced record in the read-only mode.
Example
You have created a Preview form for the Timezone table and added some fields like shown in the screenshot above (these are the Title, Name, UTC Offset, Active, and Updated at fields). And by clicking on the field referenced to the Timezone table on other forms (for example, User, Employee, Schedule, and so on), the timezone record Preview form appears.
Configuring a portal form view
Adding view for a portal page
To create a new view for a portal page element (of a record in a particular table), set up a widget instance and enter the name of the created view as this:
"itemView":"Custom View"
Creating view for a user
ПРЕИМУЩЕСТВА:
Виден ли другим юзерам? Ставится по дефолту или нужно выбирать? Как соотносится с преференсами?
To create a new view, please complete the steps below:
- Navigate to System Definition → Form Views.
- Click New and fill in the fields.
- Click Save or Save and Exit to apply changes.
View form fields
Field | Mandatory | Description |
---|---|---|
Table | Y | Specify a table for which you create a new view. This field is referenced to the Tables dictionary. |
User | N | Specify a user who will be shown this view. If the user is not specified, all users will see this view. |
Title | Y | Enter the descriptive title for the view. |
Client-side scripts on views
If there is more than one form view available for any table, then you are able to run separate Client Scripts on different views depending on the business need. In the above example, different client-side scripts can be executed on the agent and portal views if needed. So, if you need to execute your client-side script on a particular view, specify it in the relevant field when filling a form.
- No labels