MyCases configuration files are XML files that describe how a single implementation of MyCases should operate. Multiple versions of MyCases can be active on the same website, by having multiple configuration files in the Self-service Extensions folder. The configuration files must follow the naming convention: <Name>.mycases.config. The name must be unique among MyCases extensions and Self-service extensions. The name will affect the URL of the MyCases implementation, but has no other effect.
This is the root element of the configuration file.
This element declares which identity provider to use for authentication of the end-user.
This element declares references to validations to perform on login.
This element declares a single reference to a specific validation.
The referenced validator must be declared using the XML element <Validators>.
This type of element declares available validators.
This element declares an external validator and the parameters needed to invoke it.
External validators are webservices that take care of the actual validation of user input, which opens up for far more complex validation rules than can be implemented directly in the F2 Self-service framework.
External validation works by passing selected user input to the external service and letting the service respond with a passed/failed status.
The API definition for external validators are described in the F2 Self-service manual.
Use JSON formating for external validation requests.
Use multipart/form-data formating for external validation requests.
This element represents authorization configuration for external validation. Insert shared secret as inner text for simple plain text authorization (not recommended) or use the sub-element JwtAuthorization for secure authorization.
This element declares an internal validator.
This type of element declares inputs.
This type of element declares an input. The content of the element declares which internal variable to pass to the external service.
This type of element declares outputs.
This type of element declares an output. The content of the element declares the mergefield name of the value. The content must match the column names given in the SQL of the custom query.
This type of element declares custom queries.
This type of element declares a custom query.
This element represents authorization configuration for external requests.
This element represents configuration of JWT authorization for external requests.
With JWT authorization, the system will issue a Javascript Web Token (JWT) for the external service to verify. The JWT will be issued by http://cbrain.com/f2/self-service/ and use the specified value of Receiver for the subject and audience fields in the JWT. The JWT will be signed using the specified value of Secret.
The final JWT is include in the HTTP Authorization header with the scheme BEARER.
This element declares the languages available for the submission.
This element declares a single language to be available in the submission.
This type declares the pages of the layout.
This element declares the main page of the layout.
This type declares the details page of a case.
This type declares a layout based on a custom query.
This element declares a layout which displayes the result of a custom query.
This element declares a table layout.
This element declares the columns to include in a table.
This element declares a column in a table.
This element declares a layout based on a panel.
This element declares a grid based layout with rows and columns.
This element declares a row in a grid.
This element declares a cell in a row. The inner content of the cell element represents the inner layout of the cell.
This is a shared layout element group that declares a number of common layout elements.
This element declares plain text or HTML content merged with values from the custom query. The values can be merged using the $X$ syntax.
The text will be translated before merging if there is a translation available.
This element declares a button which lets the user create a new self-service reply. This can be used as a means of communication where the user may create unsolicited requests without a preceding invitation - with the request being added to a specific F2 case.
In order to add the request to the correct F2 case, the custom query data must have a certain structure:
The inner text is the text of the button. Text merging with $X$ syntaxt is supported.
This element declares a button which, when clicked, will take the user to a different page. The inner text is the text of the button with support for text merging using $X$.
The id for the page will be the id of the custom query row for which the button was rendered.
This element declares a link which references a combined PDF of everything related to a specific matter. The inner text of the element will be the text of the link with support for text merging using $X$.
This element declares a link which references the PDF version of a F2 document. The inner text of the element will be the text of the link with support for text merging using $X$.
This element declares a message to be shown each time the user returns from creating a new self-service reply.
The message will be shown as an information box embedded in the page.
The message will only be shown once right after the user have submitted the reply.
The inner-text of this element represents the text of the message and supports HTML with text merging using $X$ syntax.