bpm-core 0.0.116 → 0.0.121

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,30 +1,59 @@
1
- # BpmCore
2
-
3
- This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 18.2.0.
4
-
5
- ## Code scaffolding
6
-
7
- Run `ng generate component component-name --project bpm-core` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project bpm-core`.
8
- > Note: Don't forget to add `--project bpm-core` or else it will be added to the default project in your `angular.json` file.
9
-
10
- ## Build
11
-
12
- Run `ng build bpm-core` to build the project. The build artifacts will be stored in the `dist/` directory.
13
-
14
- ## Publishing
15
-
16
- After building your library with `ng build bpm-core`, go to the dist folder `cd dist/bpm-core` and run `npm publish`.
17
-
18
- ## Running unit tests
19
-
20
- Run `ng test bpm-core` to execute the unit tests via [Karma](https://karma-runner.github.io).
21
-
22
- ## Further help
23
-
24
- To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
25
-
26
-
27
- >`{
28
- "name": "bpm-core",
29
- "version": "0.0.2"
30
- }`
1
+ ## Recently Added Features
2
+ - ### Time Picker (Requires Angular Material 19.0.0 or Higher)
3
+ To use it, import `TimepickerComponent` in your TypeScript file and add `<app-timepicker>` to your template. For more information, hover over the selector after adding it to your template.
4
+ - ### Summary Section / Stage
5
+ This is a stage that appears before the request stage.
6
+
7
+ To enable this feature:
8
+ - The summary section **must be the first item** in the `workflowSteps` list.
9
+ - The `details` object for this step must include the following property:
10
+
11
+ ```json
12
+ "stage0": {
13
+ "isStage0": "true"
14
+ }
15
+ ```
16
+
17
+ **Example of a full payload:**
18
+
19
+ <details>
20
+ <summary>Click to expand full JSON payload</summary>
21
+
22
+ ```json
23
+ {
24
+ "data": {
25
+ "requester": { ... },
26
+ "workflowSteps": [
27
+ {
28
+ "actor": {
29
+ "recipient": {
30
+ "role": "stage0"
31
+ }
32
+ },
33
+ "details": {
34
+ "litigantType": "",
35
+ "other": "",
36
+ "requestType": "",
37
+ "reqSubject": "",
38
+ "claimValue": "",
39
+ "subClassification": "",
40
+ "reqDetails": "",
41
+ "plainName": "",
42
+ "stage0": {
43
+ "isStage0": "true"
44
+ }
45
+ }
46
+ },
47
+ {
48
+ "actor": { ... },
49
+ "date": "",
50
+ "details": { ... }
51
+ }
52
+ ],
53
+ "request": { ... },
54
+ "form": { ... }
55
+ },
56
+ "meta": { ... }
57
+ }
58
+ ```
59
+ </details>