Skip to content

URL

On certain data fetch rules (e.g. Activity and Resource) a URL parameter can be set (see screenshot below). This is used to construct the url string that will be displayed on the Activity or Resource Details of activities or resources on the PSO Workbench.

Data Fetch Rule example

The URL is constructed by combining the base URL for IFS Aurena and adding the specific form to navigate to, including parameters where this is required.

Example:

https://myifscloudaddress.com/main/ifsapplications/web/page/PersonnelFile/EmployeeForm;$filter=CompanyId eq '10' and EmpNo eq '1002'

The base part of the URL is added automatically. The page and the parameters are defined in the URL Property in the Scheduling model:

resource Resource {
    URL = "page/PersonnelFile/EmployeeForm;$filter=CompanyId eq '${url_company}' and EmpNo eq '${url_emp_no}'";

...

For URLs that correspond to the resource or activity the user is looking at, i.e. Activity or Resource Details, the URL property can contain parameters. These parameters are marked by starting with a dollar sign and the parameter being within curly brackets, i.e.:

${parameter_name}

The name of these parameters must start with 'url_' and must be used as aliases within the select.

For example, if the URL is set to "page/PersonnelFile/EmployeeForm;$filter=CompanyId eq '${url_company}' and EmpNo eq '${url_emp_no}'", the ${url_company} and ${url_emp_no} parts of the URL string are parameters. These parameters correspond to aliases within the select of the data fetch:

resource Resource {
    URL = "page/PersonnelFile/EmployeeForm;$filter=CompanyId eq '${url_company}' and EmpNo eq '${url_emp_no}'";
    SELECT
        -- mandatory columns
        'IFS' id,
        -- optional columns
        'Company' url_company,
        'Employee No' url_emp_no
    FROM dual;
}

If however a custom parameter is not required, a value from the scheduling table can be used, e.g. Activity.id or Resource.id. To use this type of URL string construction the parameter needs to be of the form:

${TableName.ColumnName}, e.g. ${Activity.id}

If the table is not specified, the table name will be assumed from the data fetch. E.g. if the URL property is set on the Activity data fetch rule, the Activity table will be assumed.

${ColumnName}, e.g. ${id}