mirror of
https://github.com/Alfresco/alfresco-ng2-components.git
synced 2025-07-24 17:32:15 +00:00
[ADF-4067] Process Service Cloud change applicationName input (#4299)
* [ADF-4047] Process Service Cloud change applicationName input * [ADF-4067] Change applicationName properties and route param name
This commit is contained in:
Silviu Popa
committed by
Eugenio Romano
Eugenio Romano
parent
3a93e07366
commit
877c57b356
@@ -27,8 +27,8 @@ Shows Process Filter Details.
|
||||
```html
|
||||
<adf-cloud-edit-process-filter
|
||||
[id]="processFilterId"
|
||||
[appName]="applicationName"
|
||||
[filterProperties]="filterProperties"
|
||||
[appName]="appName"
|
||||
[filterProperties]="filterProperties"s
|
||||
(filterChange)="onFilterChange($event)"
|
||||
(action)="onAction($event)">
|
||||
</adf-cloud-edit-process-filter>
|
||||
@@ -62,13 +62,13 @@ Use the `appName` and `id` properties to choose which process filter to edit:
|
||||
```html
|
||||
<adf-cloud-edit-process-filter
|
||||
[id]="processFilterId"
|
||||
[appName]="applicationName">
|
||||
[appName]="appName">
|
||||
</adf-cloud-edit-process-filter>
|
||||
```
|
||||
|
||||
### Filter properties
|
||||
|
||||
You can supply various _filter properties_ to edit that will determine
|
||||
You can supply various _filter properties_ to edit that will determine
|
||||
which processes are found by a filter. The full set of properties is
|
||||
given below:
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ Edits Task Filter Details.
|
||||
```html
|
||||
<adf-cloud-edit-task-filter
|
||||
[id]="taskFilterId"
|
||||
[appName]="applicationName"
|
||||
[appName]="appName"
|
||||
[filterProperties]="filterProperties"
|
||||
(filterChange)="onFilterChange($event)"
|
||||
(action)="onAction($event)">
|
||||
@@ -51,13 +51,13 @@ Use the `appName` and `id` properties to choose which task filter to edit:
|
||||
```html
|
||||
<adf-cloud-edit-task-filter
|
||||
[id]="taskFilterId"
|
||||
[appName]="applicationName">
|
||||
[appName]="appName">
|
||||
</adf-cloud-edit-task-filter>
|
||||
```
|
||||
|
||||
### Filter properties
|
||||
|
||||
You can supply various *filter properties* to edit that will determine
|
||||
You can supply various *filter properties* to edit that will determine
|
||||
which tasks are found by a filter. The full set of properties is
|
||||
given below:
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ Renders a list containing all the process instances matched by the parameters sp
|
||||
|
||||
```html
|
||||
<adf-cloud-process-list
|
||||
[applicationName]="'app-name'">
|
||||
[appName]="'app-name'">
|
||||
</adf-cloud-process-list>
|
||||
```
|
||||
|
||||
@@ -51,7 +51,7 @@ when the process list is empty:
|
||||
| Name | Type | Default value | Description |
|
||||
| ---- | ---- | ------------- | ----------- |
|
||||
| appVersion | `string` | "" | The related application version. |
|
||||
| applicationName | `string` | "" | The name of the application. |
|
||||
| appName | `string` | "" | The name of the application. |
|
||||
| businessKey | `string` | "" | Filter the tasks to display only the ones with this businessKey value. |
|
||||
| id | `string` | "" | Filter the processes to display only the ones with this ID. |
|
||||
| initiator | `string` | "" | Name of the initiator of the process. |
|
||||
@@ -100,7 +100,7 @@ You can define a custom schema for the list in the `app.config.json` file and ac
|
||||
|
||||
```html
|
||||
<adf-cloud-process-list
|
||||
[applicationName]="'appName'">
|
||||
[appName]="'appName'">
|
||||
</adf-cloud-process-list>
|
||||
```
|
||||
|
||||
@@ -133,7 +133,7 @@ information defined in `app.config.json` as in the example below:
|
||||
|
||||
```html
|
||||
<adf-cloud-process-list
|
||||
[applicationName]="'appName'" >
|
||||
[appName]="'appName'" >
|
||||
<data-columns>
|
||||
<data-column key="key" title="title" class="full-width name-column">
|
||||
<ng-template let-entry="$implicit">
|
||||
@@ -157,7 +157,7 @@ let sorting = [{ orderBy: 'status', direction: 'desc' }];
|
||||
|
||||
```html
|
||||
<adf-cloud-process-list
|
||||
[applicationName]="'appName'"
|
||||
[appName]="'appName'"
|
||||
[sort]="sorting">
|
||||
</adf-cloud-process-list>
|
||||
```
|
||||
|
||||
@@ -15,7 +15,7 @@ Shows all the information related to a task.
|
||||
|
||||
```html
|
||||
<adf-cloud-task-header
|
||||
[appName]="applicationName"
|
||||
[appName]="appName"
|
||||
[taskId]="taskId">
|
||||
</adf-cloud-task-header>
|
||||
```
|
||||
@@ -39,12 +39,12 @@ Shows all the information related to a task.
|
||||
|
||||
## Details
|
||||
|
||||
The component populates an internal array of
|
||||
The component populates an internal array of
|
||||
[CardViewModel](../core/card-view.component.md) with the information that we want to display.
|
||||
|
||||
By default all properties are displayed:
|
||||
|
||||
**_assignee_**, **_status_**, **_priority_**, **_dueDate_**, **_category_**, **_parentName_**, **_created_**, **_id_**, **_description_**, **_formName_**.
|
||||
**_assignee_**, **_status_**, **_priority_**, **_dueDate_**, **_category_**, **_parentName_**, **_created_**, **_id_**, **_description_**, **_formName_**.
|
||||
|
||||
However, you can also choose which properties to show using a configuration in `app.config.json`:
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Renders a list containing all the tasks matched by the parameters specified.
|
||||
|
||||
```html
|
||||
<adf-cloud-task-list
|
||||
[applicationName]="'APPLICATION-NAME'" >
|
||||
[appName]="'APPLICATION-NAME'" >
|
||||
</adf-cloud-task-list>
|
||||
```
|
||||
|
||||
@@ -51,7 +51,7 @@ when the task list is empty:
|
||||
|
||||
| Name | Type | Default value | Description |
|
||||
| ---- | ---- | ------------- | ----------- |
|
||||
| applicationName | `string` | "" | The name of the application. |
|
||||
| appName | `string` | "" | The name of the application. |
|
||||
| assignee | `string` | "" | The assignee of the process. Possible values are: "assignee" (the current user is the assignee), "candidate" (the current user is a task candidate", "group_x" (the task is assigned to a group where the current user is a member, no value (the current user is involved). |
|
||||
| createdDate | `string` | "" | Filter the tasks. Display only tasks created on the supplied date. |
|
||||
| dueDate | `string` | "" | Filter the tasks. Display only tasks with dueDate equal to the supplied date. |
|
||||
@@ -153,7 +153,7 @@ You can use an HTML-based schema and an `app.config.json` custom schema declarat
|
||||
|
||||
```html
|
||||
<adf-cloud-task-list
|
||||
[applicationName]="'ApplicationName'">
|
||||
[appName]="'appName'">
|
||||
<data-columns>
|
||||
<data-column key="assignee" title="Assignee" class="full-width name-column">
|
||||
<ng-template let-entry="$implicit">
|
||||
@@ -187,7 +187,7 @@ The Tasklist also supports pagination as shown in the example below:
|
||||
|
||||
```html
|
||||
<adf-cloud-task-list #taskCloud
|
||||
[applicationName]="'APPLICATION-NAME'">
|
||||
[appName]="'APPLICATION-NAME'">
|
||||
</adf-cloud-task-list>
|
||||
<adf-pagination [target]="taskCloud"
|
||||
(changePageSize)="onChangePageSize($event)">
|
||||
|
||||
Reference in New Issue
Block a user