# APS Form Component - [Library Contents](#library-contents) * [Components](#components) * [Services](#services) - [Prerequisites](#prerequisites) - [Install](#install) - [Form Component](#form-component) * [Properties](#properties) + [Form Field Validators](#form-field-validators) * [Advanced properties](#advanced-properties) * [Events](#events) * [Custom empty form template](#custom-empty-form-template) * [Controlling outcome execution behaviour](#controlling-outcome-execution-behaviour) - [Activiti Content Component](#activiti-content-component) * [Properties](#properties-1) * [Events](#events-1) - [ADF Form List Component](#adf-form-list-component) * [Properties](#properties-2) - [FormService Service](#formservice-service) * [Events](#events-2) * [Methods](#methods) - [Common scenarios](#common-scenarios) * [Changing field value based on another field](#changing-field-value-based-on-another-field) * [Listen all form Events](#listen-all-form-events) - [See also](#see-also) - [Build from sources](#build-from-sources) - [NPM scripts](#npm-scripts) - [Demo](#demo) - [License](#license) See it live: [Form Quickstart](https://embed.plnkr.co/YSLXTqb3DtMhVJSqXKkE/) ## Library Contents ### Components - [ActivitiForm](#activitiform-component) - ActivitiStartForm ### Services - [FormService](#formservice) - ActivitiAlfrescoContentService - EcmModelService - FormRenderingService - NodeService - WidgetVisibilityService ## Prerequisites Before you start using this development framework, make sure you have installed all required software and done all the necessary configuration, see this [page](https://github.com/Alfresco/alfresco-ng2-components/blob/master/PREREQUISITES.md). > If you plan to use this component with projects generated by Angular CLI, you can read more in [Using ADF with Angular CLI](https://github.com/Alfresco/alfresco-ng2-components/wiki/Angular-CLI) ## Install ```sh npm install ng2-activiti-form ``` ## Form Component The component shows a Form from Activiti ```html ``` **Display form instance by task id:** ```html ``` For an existing Task both form and values will be fetched and displayed. **Display form definition by form id:** ```html ``` Only form definition will be fetched. **Display form definition by form name:** ```html ``` **Display form definition by ECM nodeId:** In this case the metadata of the node are showed in an activiti Form. If there is no form definied in activiti for the type of the node, a new form will be automaticaly created in Activiti. ```html ``` **Display form definition by form name, and store the form field as metadata:** The param nameNode is optional. ```html ``` **Display form definition by ECM nodeId:** In this case the metadata of the node are shown in an activiti Form, and store the form field as metadata. The param nameNode is optional. ```html ``` ### Properties The recommended set of properties can be found in the following table: | Name | Type | Default | Description | | --- | --- | --- | --- | | taskId | string | | Task id to fetch corresponding form and values. | | formId | string | | The id of the form definition to load and display with custom values. | | formName | string | | Name of the form definition to load and display with custom values. | | data | FormValues | | Custom form values map to be used with the rendered form. | | showTitle | boolean | true | Toggle rendering of the form title. | | showCompleteButton | boolean | true | Toggle rendering of the `Complete` outcome button. | | disableCompleteButton | boolean | false | The `Complete` outcome button is shown but it will be disabled. | | showSaveButton | boolean | true | Toggle rendering of the `Save` outcome button. | | readOnly | boolean | false | Toggle readonly state of the form. Enforces all form widgets render readonly if enabled. | | showRefreshButton | boolean | true | Toggle rendering of the `Refresh` button. | | showValidationIcon | boolean | true | Toggle rendering of the validation icon next form title. | | saveMetadata | boolean | false | Store the value of the form as metadata. | | path | string | | Path of the folder where to store the metadata. | | nameNode | string | true | Name to assign to the new node where the metadata are stored. | | fieldValidators | FormFieldValidator[] | *see below* | Contains a list of form field validator instances. | #### Form Field Validators The Form component provides you with access to all Form Field validators. By default the following instances are created automatically: - RequiredFieldValidator - NumberFieldValidator - MinLengthFieldValidator - MaxLengthFieldValidator - MinValueFieldValidator - MaxValueFieldValidator - RegExFieldValidator - DateFieldValidator - MinDateFieldValidator - MaxDateFieldValidator If needed, you can completely redefine the set of validators used by the form. All changes to `fieldValidators` collection are automatically applied to all the further validation cycles. ##### Custom set of validators You can provide your own set of field validators based on either custom validator instances, or a mixture of default and custom ones. ```html ``` The Form component exposes a special `FORM_FIELD_VALIDATORS` constant that allows you get a quick access to all system validator instances. ```ts import { FORM_FIELD_VALIDATORS } from 'ng2-activiti-form'; @Component({...}) export class AppComponent { fieldValidators = [ // default set of ADF validators if needed ...FORM_FIELD_VALIDATORS, // custom validators new MyValidator1(), new MyValidator2() ]; } ``` ##### Custom validator example A form field validator must implement the "FormFieldValidator" interface: ```ts export interface FormFieldValidator { isSupported(field: FormFieldModel): boolean; validate(field: FormFieldModel): boolean; } ``` There might be many different validators used for various field types and purposes, so the validation layer needs every validator instance to support "isSupported" call. It is up to validator to declare support for a form field. If you want to check field types the [FormFieldTypes](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form-field-types.ts) class can help you with the predefined constants and helper methods. In addition every validator has access to all underlying APIs of the [FormFieldModel](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form-field.model.ts), including the reference to the Form instance and so other form fields. Below is a source code for a demo validator that is executed for all the "TEXT" fields, and ensures the value is not "admin", otherwise the `field.validationSummary` value is set to an error. ```ts import { FormFieldModel, FormFieldTypes, FormFieldValidator } from 'ng2-activiti-form'; export class DemoFieldValidator implements FormFieldValidator { isSupported(field: FormFieldModel): boolean { return field && field.type === FormFieldTypes.TEXT; } validate(field: FormFieldModel): boolean { if (this.isSupported(field)) { if (field.value && field.value.toLowerCase() === 'admin') { field.validationSummary = 'Sorry, the value cannot be "admin".'; return false; } } return true; } } ``` Your component can extend the default validation set instead of replacing it entirely. In the example below we redefine a default validation set with an additional "DemoFieldValidator": ```ts import { DemoFieldValidator } from './demo-field-validator'; @Component({...}) export class AppComponent { fieldValidators = [ ...FORM_FIELD_VALIDATORS, new DemoFieldValidator() ]; } ``` You can now use the 'fieldValidators' property with the Form or Task Details components to assign custom validator set for the underlying Form Model: ```html ``` Now if you run the application and try to enter "admin" in one of the text fields (either optional or required), you should see the following error: ![](docs/assets/demo-validator.png) ### Advanced properties The following properties are for complex customisation purposes: | Name | Type | Default | Description | | --- | --- | --- | --- | | form | FormModel | | Underlying form model instance. | | showDebugButton | boolean | false | Toggle debug options. | | debugMode | boolean | false | Toggle debug mode, allows displaying additional data for development and debugging purposes. | ### Events | Name | Return Type | Description | | --- | --- | --- | | formLoaded | [FormModel](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form.model.ts) | Invoked when form is loaded or reloaded. | | formSaved | [FormModel](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form.model.ts) | Invoked when form is submitted with `Save` or custom outcomes. | | formCompleted | [FormModel](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form.model.ts) | Invoked when form is submitted with `Complete` outcome. | | formDataRefreshed | [FormModel](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form.model.ts) | Invoked when form values are refreshed due to a data property change | | executeOutcome | [FormOutcomeEvent](https://github.com/Alfresco/alfresco-ng2-components/blob/master/ng2-components/ng2-activiti-form/src/components/widgets/core/form-outcome-event.model.ts) | Invoked when any outcome is executed, default behaviour can be prevented via `event.preventDefault()` | | onError | any | Invoked at any error | All `form*` events receive an instance of the `FormModel` as event argument for ease of development: **MyView.component.html** ```html ``` **MyView.component.ts** ```ts onFormSaved(form: FormModel) { console.log(form); } ``` ### Custom empty form template You can add a template that will be show if no form definition has been found ```html

Empty form

``` ### Controlling outcome execution behaviour If absolutely needed it is possible taking full control over form outcome execution by means of `executeOutcome` event. This event is fired upon each outcome execution, both system and custom ones. You can prevent default behaviour by calling `event.preventDefault()`. This allows for example having custom form validation scenarios and/or additional validation summary presentation. Alternatively you may want just running additional code on outcome execution without suppressing default one. **MyView.component.html** ```html ``` **MyView.component.ts** ```ts import { FormOutcomeEvent } from 'ng2-activiti-form'; export class MyView { validateForm(event: FormOutcomeEvent) { let outcome = event.outcome; // you can also get additional properties of outcomes // if you defined them within outcome definition if (outcome) { let form = outcome.form; if (form) { // check/update the form here event.preventDefault(); } } } } ``` There are two additional functions that can be of a great value when controlling outcomes: - `saveTaskForm()` - saves current form - `completeTaskForm(outcome?: string)` - save and complete form with a given outcome name **Please note that if `event.preventDefault()` is not called then default outcome behaviour will also be executed after your custom code.** ## Activiti Content Component The component shows the content preview. ```html ``` ### Properties The recommended set of properties can be found in the following table: | Name | Type | Default | Description | | --- | --- | --- | --- | | contentId | string | | The content id to show. | ### Events | Name | Description | | --- | --- | | contentClick | Invoked when the content is clicked. | ## ADF Form List Component The component shows the activiti forms as a list. ```html ``` ### Properties The recommended set of properties can be found in the following table: | Name | Type | Default | Description | | --- | --- | --- | --- | | forms | any | | The array that contains the information to show inside the list. | ## FormService Service ```ts import { FormService, FormEvent, FormFieldEvent } from 'ng2-activiti-form'; @Component(...) class MyComponent { constructor(formService: FormService) { formService.formLoaded.subscribe( (e: FormEvent) => { console.log(`Form loaded: ${e.form.id}`); } ); formService.formFieldValueChanged.subscribe( (e: FormFieldEvent) => { console.log(`Field value changed. Form: ${e.form.id}, Field: ${e.field.id}, Value: ${e.field.value}`); } ); } } ``` ### Events | Name | Args Type | Description | | --- | --- | --- | | formLoaded | FormEvent | Raised when form has been loaded or reloaded | | formFieldValueChanged | FormFieldEvent | Raised when input values change | | taskCompleted | FormEvent | Raised when a task is completed successfully | | taskCompletedError | FormErrorEvent | Raised when a task is completed unsuccessfully | | taskSaved | FormEvent | Raised when a task is saved successfully | | taskSavedError | FormErrorEvent | Raised when a task is saved unsuccessfully | | executeOutcome | FormOutcomeEvent | Raised when a form outcome is executed | | formEvents | Event | You can subscribe to this event to listen : ( click, blur, change, focus, focusin, focusout, input, invalid, select) of any elements in the form , see doc below | | validateForm | ValidateFormEvent | Raised each time a form is validated. You can use it to provide custom validation or prevent default behaviour. | | validateFormField | ValidateFormFieldEvent | Raised each time a form field is validated. You can use it to provide custom validation or prevent default behaviour.| ### Methods | Name | Params | Returns | Description | | --- | --- | --- | --- | | createFormFromANode | (formName: string) | Observable\ | Create a Form with a fields for each metadata properties | | createForm | (formName: string) | Observable\ | Create a Form | | addFieldsToAForm | (formId: string, formModel: FormDefinitionModel) | Observable\ | Add Fileds to A form | | searchFrom | (name: string) | Observable\ | Search For A Form by name | | getForms | n/a | Observable\ | Get All the forms | | getProcessDefinitions | n/a | Observable\ | Get Process Definitions | | getTasks | n/a | Observable\ | Get All the Tasks | | getTask | (taskId: string) | Observable\ | Get Task | | saveTaskForm | (taskId: string, formValues: FormValues) | Observable\ | Save Task Form | | completeTaskForm | (taskId: string, formValues: FormValues, outcome?: string) | Observable\ | Complete Task Form | | getTaskForm | (taskId: string) | Observable\ | Get Form related to a taskId | | getFormDefinitionById | (formId: string) | Observable\ | Get Form Definition | | getFormDefinitionByName | (name: string) | Observable\ | Returns form definition by a given name. | | getStartFormInstance | (processId: string) | Observable\ | Get start form instance for a given processId | | getStartFormDefinition | (processId: string) | Observable\ | Get start form definition for a given process | | createTemporaryRawRelatedContent | (file: any) | Observable\ | Save File | | getRestFieldValues | (taskId: string, field: string) | Observable\ | | | getRestFieldValuesByProcessId | (processDefinitionId: string, field: string) | Observable\ | | | getRestFieldValuesColumnByProcessId | (processDefinitionId: string, field: string, column?: string) | Observable\ | | | getRestFieldValuesColumn | (taskId: string, field: string, column?: string) | Observable\ | | | getWorkflowGroups\ | (filter: string, groupId?: string) | Observable\ | | | getWorkflowUsers\ | (filter: string, groupId?: string) | Observable\ | | ## Common scenarios ### Changing field value based on another field Create a simple Form with a dropdown widget (id: `type`), and a multiline text (id: `description`). ```ts formService.formFieldValueChanged.subscribe((e: FormFieldEvent) => { if (e.field.id === 'type') { const fields: FormFieldModel[] = e.form.getFormFields(); const description = fields.find(f => f.id === 'description'); if (description != null) { console.log(description); description.value = 'Type set to ' + e.field.value; } } }); ``` You subscribe to the `formFieldValueChanged` event and check whether event is raised for the `type` widget, then you search for a `description` widget and assign its value to some simple text. The result should be as following: ![](docs/assets/form-service-sample-01.png) ### Listen all form Events If you want to listen all the events fired in the form you can subscribe to this Subject : ```ts formService.formEvents.subscribe((event: Event) => { console.log('Event fired:' + event.type); console.log('Event Target:' + event.target); }); ``` ## See also - [Form Stencils with Angular 2](docs/stencils.md) - [Form Extensibility and Customisation](docs/extensibility.md). ## Build from sources You can build the component from sources with the following commands: ```sh npm install npm run build ``` > The `build` task rebuilds all the code, runs tslint, license checks > and other quality check tools before performing unit testing. ## NPM scripts | Command | Description | | --- | --- | | npm run build | Build component | | npm run test | Run unit tests in the console | | npm run test-browser | Run unit tests in the browser | npm run coverage | Run unit tests and display code coverage report | ## Demo Please check the demo folder for a demo project ```sh cd demo npm install npm start ``` ## License [Apache Version 2.0](https://github.com/Alfresco/alfresco-ng2-components/blob/master/LICENSE)