-
Notifications
You must be signed in to change notification settings - Fork 188
/
common-workflows-3.xsd
1605 lines (1540 loc) · 65.1 KB
/
common-workflows-3.xsd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<!--
~ Copyright (c) 2010-2017 Evolveum
~
~ Licensed under the Apache License, Version 2.0 (the "License");
~ you may not use this file except in compliance with the License.
~ You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
-->
<xsd:schema targetNamespace="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:a="http://prism.evolveum.com/xml/ns/public/annotation-3"
xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:t="http://prism.evolveum.com/xml/ns/public/types-3"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
elementFormDefault="qualified"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
jaxb:extensionBindingPrefixes="xjc"
jaxb:version="2.0">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
<!-- Don't provide schemaLocation here, as it causes xjc to really contact the URIs (!) -->
<xsd:import namespace="http://prism.evolveum.com/xml/ns/public/annotation-3"/>
<xsd:import namespace="http://prism.evolveum.com/xml/ns/public/types-3"/>
<xsd:include schemaLocation="http://midpoint.evolveum.com/xml/ns/public/common/common-core-3" />
<xsd:complexType name="ApprovalSchemaType">
<xsd:annotation>
<xsd:documentation>
Rules for approving something (e.g. assignment of a role to a user).
Specifies the structure of approvers and their relations.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="name" type="xsd:string" minOccurs="0"/>
<xsd:element name="description" type="xsd:string" minOccurs="0"/>
<xsd:element name="level" type="c:ApprovalStageDefinitionType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Levels, or stages, of the approval process.
</xsd:documentation>
<xsd:appinfo>
<a:deprecated>true</a:deprecated>
<a:deprecatedSince>3.6</a:deprecatedSince>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="stage" type="c:ApprovalStageDefinitionType" minOccurs="1" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Levels, or stages, of the approval process.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ApprovalStageDefinitionType">
<xsd:annotation>
<xsd:documentation>
One "level" (or stage) in the approval process.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="order" type="xsd:int" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Order of this approval stage. DEPRECATED. Use "number" instead.
</xsd:documentation>
<xsd:appinfo>
<a:deprecated>true</a:deprecated>
<a:deprecatedSince>3.6</a:deprecatedSince>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="number" type="xsd:int" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Number of this approval stage. These should go from 1 to N.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="name" type="xsd:string" minOccurs="0"/>
<xsd:element name="displayName" type="xsd:string" minOccurs="0"/>
<xsd:element name="description" type="xsd:string" minOccurs="0"/>
<xsd:element name="approverRef" type="c:ObjectReferenceType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Instruction to approve something, by a user (if this points to a User object) or
by someone from a group of users (if this points to a Org object; representing
all users that belong to that organization).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="approverRelation" type="xsd:QName" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<p>
What relation(s) to use when determining approvers? E.g. "approver", "owner",
"securityApprover", and so on.
</p>
</xsd:documentation>
<xsd:appinfo>
<a:since>3.5</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="approverExpression" type="c:ExpressionType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Dynamically specifies approver(s). If specified, the expression(s) are evaluated and the result
is used as a set of approvers (UserType, OrgType, RoleType, or any combination of them).
May be used with approverRef element(s).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="evaluationStrategy" type="c:LevelEvaluationStrategyType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Must all approvers at this stage approve the thing (allMustApprove),
or first decision is taken as authoritative (firstDecides)?
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="outcomeIfNoApprovers" type="c:ApprovalLevelOutcomeType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
What is the outcome (of this stage) if there are no approvers? E.g. there are no users that have
been assigned a role as an approver; or a user has no managers, etc.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="groupExpansion" type="c:GroupExpansionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
How should be "groups" (orgs, roles) expanded? Default is "byClaimingWorkItem", i.e. they are not
expanded at all - their members can claim corresponding work items.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="formRef" type="c:ObjectReferenceType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Form to be displayed e.g. to present or request additional information.
EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!-- TODO some hooks to allow ad-hoc customizations like making a form field obligatory or optional depending on the stage etc. -->
<xsd:element name="additionalInformation" type="c:ExpressionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Additional information for approver. Will be displayed when work item will be worked on.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="automaticallyApproved" type="c:ExpressionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Condition specifying when this stage is automatically approved (e.g. "user is
from Board of Directors"). This is an expression that should yield a boolean value.
DEPRECATED. Use automaticallyCompleted instead.
</xsd:documentation>
<xsd:appinfo>
<a:deprecated>true</a:deprecated>
<a:deprecatedSince>3.6</a:deprecatedSince>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="automaticallyCompleted" type="c:ExpressionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Expression specifying that this stage should be automatically processed (approved, rejected, skipped).
If the expression returns null, standard processing by human actors is carried out.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="duration" type="xsd:duration" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Duration of work items created at this stage.
TODO other time units, like business days?
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="timedActions" type="tns:WorkItemTimedActionsType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
What actions are to be applied to work items when given timer(s) occur.
EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ApprovalSchemaExecutionInformationType">
<xsd:annotation>
<xsd:documentation>
Information on actual or expected execution of an approval schema.
Contains information on the approval schema stages as defined, as executed, and as estimated to be executed.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="taskRef" type="c:ObjectReferenceType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The task that was or would be created to approve give operation. This object reference should
contain the actual object (TODO).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="currentStageNumber" type="xsd:int" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Current stage, if any. Null usually means that the approval process has not started yet.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="stage" type="c:ApprovalStageExecutionInformationType" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Information related to a given stage of the approval process.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="policyRules" type="tns:SchemaAttachedPolicyRulesType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ApprovalStageExecutionInformationType">
<xsd:annotation>
<xsd:documentation>
Information of an actual or expected execution of an approval stage.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="number" type="xsd:int" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Number of this approval stage. May be missing if the stage definition and its number is provided.
If both numbers are present, they must be equal.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="definition" type="c:ApprovalStageDefinitionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Definition of this approval stage.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="executionRecord" type="c:ApprovalStageExecutionRecordType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Approvers that are expected to be part of this stage.
(Some might be "for sure" and some might be "expected", but currently we do not distinguish between these.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="executionPreview" type="c:ApprovalStageExecutionPreviewType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ApprovalStageExecutionPreviewType">
<xsd:annotation>
<xsd:documentation>
Preview of an execution of an approval stage.
Contains estimation of what approvers there would be; also - if applicable - any result
that is expected to be automatically determined, and so on.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="expectedApproverRef" type="c:ObjectReferenceType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Approvers that are expected to be part of this stage.
(Some might be "for sure" and some might be "expected", but currently we do not distinguish between these.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="expectedAutomatedOutcome" type="c:ApprovalLevelOutcomeType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Expected outcome that would occur automatically, i.e. not based on the decision of human approvers.
E.g. in case of no approvers, or because of automaticallyApproved/automaticallyCompleted feature.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="expectedAutomatedCompletionReason" type="c:AutomatedCompletionReasonType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Reason of expected automated completion.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="errorMessage" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Error message if preview couldn't be computed. (TODO)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ApprovalStageExecutionRecordType">
<xsd:annotation>
<xsd:documentation>
Record of an actual execution of an approval stage.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="event" type="c:CaseEventType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Events related to this stage. Currently might contain WorkItemEventType and StageCompletionEventType instances.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="workItem" type="c:WorkItemType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Currently active work items.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="ApprovalLevelOutcomeType">
<xsd:annotation>
<xsd:documentation>
Result (outcome) of an approval process stage.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="approve">
<xsd:annotation>
<xsd:documentation>
Operation was approved at this stage. The approval process will continue at the next stage.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="APPROVE"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="reject">
<xsd:annotation>
<xsd:documentation>
Operation was rejected at this stage. The approval process will stop.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="REJECT"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="skip">
<xsd:annotation>
<xsd:documentation>
This stage is silently skipped. This is useful for situations where we don't even want to start
an approval process if there are no approvers in it.
Skipping whole approval process is currently supported only partly: when using approver relations.
For approver expressions, these are always evaluated within context of a workflow process.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="SKIP"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="WorkItemResultType">
<xsd:annotation>
<xsd:documentation>
Overall output from a work item: outcome (approve/reject/...), comment, additional delta,
and probably other things in the future.
TODO devise an extension mechanism for this
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.6</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractWorkItemOutputType">
<xsd:sequence>
<xsd:element name="additionalDeltas" type="tns:ObjectTreeDeltasType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Additional delta(s) resulting from this action.
Typically if the user filled-in some information into
custom form.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="WorkItemOutcomeType">
<xsd:annotation>
<xsd:documentation>
Result (outcome) of a work item.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="approve">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="APPROVE"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="reject">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="REJECT"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<!-- TODO something like CANCEL i.e. canceled work item without providing any answer
(e.g. when replacing it with a set of other work items) -->
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GroupExpansionType">
<xsd:annotation>
<xsd:documentation>
How should be "groups" (orgs, roles) expanded?
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="byClaimingWorkItem">
<xsd:annotation>
<xsd:documentation>
Groups are not expanded at all - their members can claim corresponding work items.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="BY_CLAIMING_WORK_ITEMS"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="onWorkItemCreation">
<xsd:annotation>
<xsd:documentation>
Groups are expanded on work item creation. One work item is created for each member of given org/role.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="ON_WORK_ITEM_CREATION"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="LevelEvaluationStrategyType">
<xsd:annotation>
<xsd:documentation>
Enumeration of approval strategies at a particular stage.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="allMustApprove">
<xsd:annotation>
<xsd:documentation>
All approvers at a particular stage must approve the operation.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="ALL_MUST_AGREE"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="firstDecides">
<xsd:annotation>
<xsd:documentation>
First approver that votes will decide the whole stage (either by approving or by rejecting).
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="FIRST_DECIDES"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="WfConfigurationType">
<xsd:annotation>
<xsd:documentation>
Configuration for workflows - for those parts not stored in the system config file.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="modelHookEnabled" minOccurs="0" type="xsd:boolean" default="true">
<xsd:annotation>
<xsd:documentation>
This property controls the workflow model hook - i.e. whether each request going
through the model subsystem should be processed by the workflow hook. So, if disabled,
all requests are executed immediately, without being processed by workflows.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="processCheckInterval" minOccurs="0" type="xsd:int" default="10">
<xsd:annotation>
<xsd:documentation>
For "dumb" wf processes, which require active shadowing tasks, sets the process
instance check interval (in seconds).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="allowCompleteOthersItems" minOccurs="0" type="xsd:boolean" default="true">
<xsd:annotation>
<xsd:documentation>
Whether appropriately privileged users (e.g. the administrator) can approve/reject work items
assigned to other users.
DEPRECATED. Use authorizations to limit ability to approve/reject arbitrary work items.
</xsd:documentation>
<xsd:appinfo>
<a:deprecatedSince>3.5</a:deprecatedSince>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="useLegacyApproversSpecification" minOccurs="0" type="tns:LegacyApproversSpecificationUsageType">
<xsd:annotation>
<xsd:documentation>
How to deal with legacy approvers specifications, i.e. approvalRef, approvalExpression, approvalSchema,
automaticallyApproved items in AbstractRoleType? The default is "ifNoExplicitApprovalPolicyAction", that
means these items are applied only if no explicit approval policy action is encountered.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="useDefaultApprovalPolicyRules" minOccurs="0" type="tns:DefaultApprovalPolicyRulesUsageType">
<xsd:annotation>
<xsd:documentation>
Whether to use default approval policy rules. The default is "ifNoApprovalPolicyAction", that means
these rules are applied only if no other approval policy action is encountered.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="executionTasksSerialization" minOccurs="0" type="tns:WfExecutionTasksSerializationType">
<xsd:annotation>
<xsd:documentation>
Whether and how to serialize execution tasks (if "execute after all approvals" is set to false).
EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:since>3.6.1</a:since>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="primaryChangeProcessor" minOccurs="0" type="tns:PrimaryChangeProcessorConfigurationType" />
<xsd:element name="generalChangeProcessor" minOccurs="0" type="tns:GeneralChangeProcessorConfigurationType" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="WfExecutionTasksSerializationType">
<xsd:annotation>
<xsd:documentation>
Whether and how to serialize execution tasks (if "execute after all approvals" is set to false).
EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:since>3.6.1</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="enabled" type="xsd:boolean" minOccurs="0" default="true">
<xsd:annotation>
<xsd:documentation>
Whether this feature is enabled. Default is true if executionTasksSerialization element is present; false otherwise.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="retryInterval" type="xsd:duration" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Interval after which the execution task is to be rescheduled in case of conflict. Default is 10 seconds.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="LegacyApproversSpecificationUsageType">
<xsd:annotation>
<xsd:documentation>
How to deal with legacy approvers specifications, i.e. approvalRef, approvalExpression, approvalSchema,
automaticallyApproved items in AbstractRoleType?
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="never">
<xsd:annotation>
<xsd:documentation>
The legacy approvers specification is never used.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="NEVER"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="always">
<xsd:annotation>
<xsd:documentation>
The legacy approvers specification is always used. It is used before any other (policy-based) approval actions.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="ALWAYS"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ifNoExplicitApprovalPolicyAction">
<xsd:annotation>
<xsd:documentation>
The legacy approvers specification is used if there's no explicit approval policy applicable to a given
target.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="IF_NO_EXPLICIT_APPROVAL_POLICY_ACTION"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DefaultApprovalPolicyRulesUsageType">
<xsd:annotation>
<xsd:documentation>
Whether to use default approval policy rules.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="never">
<xsd:annotation>
<xsd:documentation>
Default approval policy rules are never used.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="NEVER"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ifNoApprovalPolicyAction">
<xsd:annotation>
<xsd:documentation>
Default approval policy rules are used if there are no applicable approval policy actions.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="IF_NO_APPROVAL_POLICY_ACTION"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="WfChangeProcessorConfigurationType">
<xsd:annotation>
<xsd:documentation>
Configuration for workflow change processor.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="enabled" minOccurs="0" type="xsd:boolean" default="true"/>
<xsd:element name="order" minOccurs="0" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
Order in which the change processor should be invoked. (Unspecified means "at the end".)
NOT IMPLEMENTED YET.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GeneralChangeProcessorConfigurationType">
<xsd:annotation>
<xsd:documentation>
Configuration for GeneralChangeProcessor.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:WfChangeProcessorConfigurationType">
<xsd:sequence>
<xsd:element name="scenario" minOccurs="0" maxOccurs="unbounded" type="tns:GeneralChangeProcessorScenarioType" />
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="GeneralChangeProcessorScenarioType">
<xsd:annotation>
<xsd:documentation>
A scenario for GeneralChangeProcessor.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="enabled" minOccurs="0" type="xsd:boolean" default="true">
<xsd:annotation>
<xsd:documentation>
Is this scenario enabled?
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="name" minOccurs="0" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A human-readable name of the scenario (e.g. "Approving assignments of roles R1001-R1999 to users in XYZ organization").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="activationCondition" minOccurs="0" type="c:ExpressionType">
<xsd:annotation>
<xsd:documentation>
A condition controlling whether this scenario applies, i.e. whether a defined approval process should be started.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="processName" minOccurs="1" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A name of the approval process. When the above condition is met, this process is started. It has to evaluate the situation,
seek user's (or users') approval(s), modifying the situation if necessary.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="beanName" minOccurs="0" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The name of the Spring bean used for customizations. It provides e.g. a method for externalizing process state,
a method for providing work item contents, and so on.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="PrimaryChangeProcessorConfigurationType">
<xsd:annotation>
<xsd:documentation>
Configuration for PrimaryChangeProcessor.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:WfChangeProcessorConfigurationType">
<xsd:sequence>
<xsd:element name="policyRuleBasedAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addUserAbstractRoleAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyUserAbstractRoleAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addUserResourceAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyUserResourceAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addAbstractRoleAbstractRoleAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyAbstractRoleAbstractRoleAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addAbstractRoleResourceAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyAbstractRoleResourceAssignmentAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addAbstractRoleAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyAbstractRoleAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addUserAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyUserAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addResourceAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="modifyResourceAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="addAssociationAspect" type="tns:PcpAspectConfigurationType" minOccurs="0" />
<xsd:element name="otherAspect" type="tns:GenericPcpAspectConfigurationType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="PcpAspectConfigurationType">
<xsd:annotation>
<xsd:documentation>
Configuration for a primary change processor aspect.
Some aspects do not require any configuration - for example, role and resource assignment ones.
They take all the approver information directly from the object (role or resource) being assigned.
However, there are some others (namely, role/resource/user/whatever add/modify aspects) that need
the explicit information about approver(s) in order to know where to route the request.
For the former aspects, the approver information specified here takes precedence over
approver information derived from the objects being used (e.g. role or resource).
More specifically, if any approver information is here, no approver information is
taken from the objects. This could be changed (e.g. by allowing to tune this behavior)
in the future.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="enabled" minOccurs="0" maxOccurs="1" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the aspect is enabled or not.
If not specified (but if aspect configuration is present), it is assumed to be true.
However, if the whole aspect configuration is absent, only aspects marked as "enabled-by-default" are enabled.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="approverRef" type="c:ObjectReferenceType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Approvers for this aspect. The approver is a person (or group) that approves carrying out
action(s) relevant to this aspect. This reference may point to object of type UserType of OrgType.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="approverExpression" type="c:ExpressionType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Approvers for this aspect. If specified, the expression(s) are evaluated and the result
is used as a set of approvers (UserType, OrgType, or any combination of them).
May be used with approverRef element(s).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="approvalSchema" type="c:ApprovalSchemaType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
More complex (multi-stage) approval schema. If used, it overrides both
approverRef and approverExpression elements.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="approvalProcess" type="xsd:string" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Name of custom approval process. If used, it overrides
approverRef, approverExpression, and approvalSchema elements.
For explicitness, only one of approverRef(s)/approverExpression(s),
approvalSchema and approvalProcess should be specified.
THIS PROPERTY (approvalProcess) IS NOT SUPPORTED YET.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="automaticallyApproved" type="c:ExpressionType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Condition specifying when the item is automatically approved (e.g. "user is
from Board of Directors"). This is an expression that should yield a boolean value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="applicabilityCondition" type="c:ExpressionType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Condition specifying if the workflow should be started in the first place.
This is an expression that should yield a boolean value. It gets 'itemToApprove' parameter
that contains item to be approved - it is aspect-specific: might be e.g. an assignment,
an association + resource shadow discriminator, etc.
The difference between applicabilityCondition and automaticallyApproved is that if the
former yields false, workflow is not even started. If it yields true, workflow is started,
and then 'automaticallyApproved' is evaluated. If it yields false, manual approval is
required. If true, item is automatically approved.
CURRENTLY IMPLEMENTED ONLY IN AddAssociationAspect.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GenericPcpAspectConfigurationType">
<xsd:annotation>
<xsd:documentation>
A generic configuration for a wf aspect.
It is meant for non-standard aspects. (Standard aspects use named properties in
PrimaryChangeProcessorConfigurationType container.)
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:PcpAspectConfigurationType">
<xsd:sequence>
<xsd:element name="name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Name of the aspect bean.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>