Page History

Portal contexts

Portal The portal context engine allows restricting you to restrict access to specified portals for some user categories defined by User Criteria. 

Example case:

1. You create two portals: Moscow Users Portal and London Users Portal.
2. You need to restrict access to these portals only for users from relevant cities.
3. Using the portal contexts engine, you can easily do this so by creating a user criteria record (in this case, you have to specify the location as a criterion).

Create a portal context

To create a portal context, please complete the steps below:

1. Navigate to Portal Structure → Context Rules → Portal Contexts.
2. Click New and fill in the fields.
3. Click Save or Save and Exitexit to apply the changes.

Portal context Context form descriptionfields

Related properties

1. You can enable or disable this engine by editing the portals.portal_context.enable property value. It is disabled by default. To enable portal context, edit the property value and type 'true'.
2. You can define roles, the owners of which disregard portal context rules and have access to all categories and items of the portal specified. For thisTo do so, edit the portals.portal_conteхt.override_roles property value and specify roles here.

Page mapping

The page mappings engine is used to configure redirect rules in case the visited link is not accessible due to role restrictions.

Example case:

1. One user sent a task link to another. The task link leads to the agent interface and looks like thisthe following way: https://instance.example.com/record/task/162306286418042670.
2. The other user does not have an agent role, so they will not be able to open and see itthe task record. But they can open portal links, respectively.
3. The page mappings engine allows creating you to create a rule which that will convert agent interface links to portal links.
4. After processing with a rule, the initial link looks like thisthe following way:
   https://instance.example.com/portal/record/?table_name=task&record_id=162306286418042670&view=SP
5. Now, the link recipient can see the link content.

Create a page mapping

---

To create a page mapping rule from scratch, please complete the steps below:

1. Navigate to Portal Structure → Context Rules → Page Mappings.
2. Click New and fill in the fields.
3. Click Save or Save and Exitexit to apply the changes.

TipIt is more effective to create page mapping rules out of the portal context rules. For this, navigate to the relevant portal context record, scroll down to the Related Lists area, open the Page Mapping tab and create rules.

Page Mapping form fields

Field	Mandatory	Description
Portal Contextcontext	Y	Specify a reference to the previously created portal context.
URL Templatetemplate	Y	Specify initial URL template. Info The value should start with a slash: /  You can use variables here. ExamplesExample: /record/{tableName}/{recordID} Note There is no limit for the variables variable name. In the example below, it can be not only {id}, but  but also {identificator}, {identify}, etc. But please keep in mind that: Variable names should be enclosed in the curly brackets, like this: {id}. Variable names in the URL Templatetemplate and Portal Pagepage should match to avoid errors.
Portal Pagepage	Y	Specify portal page URL template. This template is used to create URLs for portal pages out of URLs passed. Info The value should start with a slash: /  Example: /portal/record?table_name={tableName}&record_id={recordID}&view=SP

.