ENDOC-647 customer portal improvements #667
Conversation
| * A [Keycloak server](https://www.keycloak.org/docs/15.0/server_admin/#_email) configured with the SMTP server settings to enable email verification for users. | ||
| * Use the [Entando CLI](../../docs/getting-started/entando-cli.md) command `ent check-env develop` to verify dependencies | ||
| * A Jira Service Management account | ||
| * A [Keycloak server](https://www.keycloak.org/docs/15.0/server_admin/#_email) configured with the SMTP settings to enable email verification for users |
There was a problem hiding this comment.
delete extra space between SMTP & settings
| #### Install the Customer Portal | ||
| From the Hub Catalog, `Deploy` and `Install` the Customer Portal application first, then the content bundle | ||
|
|
||
| #### Set up permissions to configure the service |
There was a problem hiding this comment.
Capitalize main terms
Alternate header>>Assign Roles to Configure the Service
There was a problem hiding this comment.
i was going to leave these with the capitalization of regular sentences, but don't mind using header capitalization; the only reason i was doing headers instead of bold was so that i could reference a specific subsection
| 2. Click the `Service Account Roles` tab at the top of the page and select `realm-management` from the `Client Roles` field | ||
| 3. Choose `realm-admin` from `Available Roles`, then click `Add selected`. It should appear as an `Assigned Role`. | ||
|
|
||
| #### Navigate to your Customer Portal |
| * Find the `Customer Portal` folder | ||
| * From the `Actions` pull-down menu → `View Published Page` | ||
| 4. To navigate to your Customer Portal: | ||
| 1. From the sidebar, go to `Page` → `Management` |
There was a problem hiding this comment.
I swear the numbered list did not work before embedded inside another list. But good to know they work now
| ::: tip Note: | ||
| * The built-in mapper for email must be enabled on the server client so that user accounts can be retrieved from Jira and new tickets can use that account information. | ||
| ::: | ||
| >Note: The built-in mapper for email must be enabled on the server client so that user accounts can be retrieved from Jira and new tickets can use that account information. |
There was a problem hiding this comment.
I think this is important enough that it should not be in the faded format. Maybe "Note" can be bolded and the remainder can be regular format.
There was a problem hiding this comment.
i'll switch to tip format
|
|
||
| 1. Go to Customers to add organizations and projects. Once added, click on the name of the organization to get the ID, needed later, from the URL. \ | ||
| e.g. example.com/jira/servicedesk/projects/ECS/organization/3 → the Organization ID is “3” | ||
| #### To add organizations and projects in Jira: |
| * **Create a Customer or Partner**\ | ||
| Creating a `Customer` and `Partner` is a similar process. Below are the steps for adding a `Customer`. Follow the same procedure for adding a `Partner`. | ||
| #### Create a Customer or Partner | ||
| The processes to create customers and partners are similar. Below are the steps to add a `Customer`. Follow the analogous procedure to add a `Partner`. |
There was a problem hiding this comment.
analogous is a kind of a hard word for many, simpler word would make it easier to understand
| * Select the user for the `Project`. | ||
| * Click `Submit`. | ||
| #### Create and Assign Projects | ||
| From the Customer Portal landing page, click on a customer to see the associated project list. |
No description provided.