Forums Questions & Help Tags YAWL XOR Radio Button Dear all, I am trying to implement an XOR decision using radio buttons. I have totally failed to implement it. How may I successfully implement choices using XOR split with radio buttons Choice XOR split with enumeration type Radio buttons as such are not part of the standard forms that are generated by YAWL. For real radio buttons you would have to use custom forms. However, the logic of an XOR choice based on a finite selection is easy to do. You define a datatype like this: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:simpleType name="choiceType"> <xs:restriction base="xs:string"> <xs:enumeration value="A" /> <xs:enumeration value="B" /> </xs:restriction> </xs:simpleType> </xs:schema>Then you create a net variable of that type and ask for its value in the split statement as in the attached workflow specification. Let me know if that helps. Log in or register to post comments Image File xorRadioButtons.yawl (8.48 KB) Log in or register to post comments
Choice XOR split with enumeration type Radio buttons as such are not part of the standard forms that are generated by YAWL. For real radio buttons you would have to use custom forms. However, the logic of an XOR choice based on a finite selection is easy to do. You define a datatype like this: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:simpleType name="choiceType"> <xs:restriction base="xs:string"> <xs:enumeration value="A" /> <xs:enumeration value="B" /> </xs:restriction> </xs:simpleType> </xs:schema>Then you create a net variable of that type and ask for its value in the split statement as in the attached workflow specification. Let me know if that helps. Log in or register to post comments Image File xorRadioButtons.yawl (8.48 KB)
Choice XOR split with enumeration type
Radio buttons as such are not part of the standard forms that are generated by YAWL. For real radio buttons you would have to use custom forms.
However, the logic of an XOR choice based on a finite selection is easy to do. You define a datatype like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:simpleType name="choiceType"> <xs:restriction base="xs:string"> <xs:enumeration value="A" /> <xs:enumeration value="B" /> </xs:restriction> </xs:simpleType> </xs:schema>Then you create a net variable of that type and ask for its value in the split statement as in the attached workflow specification.
Let me know if that helps.