I have a cfgrid set up, and it works well when sorting and returning the correct information. The problem is that when I return a longer list that extends the page, and I select a row, I skip to another area of the returned list. It still selects the row when clicked on, but will end up somewhere else on the list so that I have to scroll down to find it. I want the page to just stay where it is and still select the row like it has been. I have messed with preservedataonsort, and anything else that may be related, but with no luck. Any thoughts to accomplish this? Thanks
<cfgrid format="HTML" name="tblbaseNEWNEWGRID" query="HOMEFILTERQRY"
selectmode="" colheaderbold="true" sort="true" selectcolor="red" selectonload="no" gridlines="yes" >
<cfgridcolumn name="B" width="74" headeralign="center" dataalign="center" />
<cfgridcolumn name="W" width="159" headeralign="center" dataalign="center" />
<cfgridcolumn name="START" width="57" header="START" headeralign="center" dataalign="center" type="date" />
<cfgridcolumn name="END" width="57" header="END" headeralign="center" dataalign="center" type="date" />
<cfgridcolumn name="POH" width="57" header="POH" headeralign="center" dataalign="center" type="date" />
<cfgridcolumn name="INSTALL" width="135" header="INSTALL" headeralign="center" dataalign="center"/>
<cfgridcolumn name="ST" width="65" headeralign="center" dataalign="center"/>
<cfgridcolumn name="PREV" width="105" header="PREVIOUS REASON" headeralign="center" dataalign="center">
<cfgridcolumn name="ES" width="75" header="COMPANY" headeralign="center" dataalign="center"/>
<cfgridcolumn name="ES" width="62" header="PUM" headeralign="center" dataalign="center"/>
<cfgridcolumn name="PUM" width="65" header="SET " headeralign="center" dataalign="center" type="numeric" />
<cfgridcolumn name="ESP_D" width="48" Header="DH?" headeralign="center" dataalign="center"/>
<cfgridcolumn name="PROVING" width="48" header="PR?" headeralign="center" dataalign="center" />
<cfgridcolumn name="MOTO" width="88" header="MOTO" headeralign="center" dataalign="center"/>
<cfgridcolumn name="COMMENTS" width="88" headeralign="center" dataalign="center"/>
<cfgridcolumn name="ADDED_BY" display="NO" values="#session.AD_User#" >
<cfgridcolumn name="ADDED_DATE" display="NO" values="#now()#" >
<cfgridcolumn name="EVENT_NUM" width="50" header="EVENT NUMBER" headeralign="center" dataalign="center" select="no" />
</cfgrid>
Related
I have deployed bpmn workflow which is creating duplicate task instances. On my further investigation I noticed the ACT_HI_ACTINST table which records sequence of activities regarding the process instance of workflow. What I found is, in b/w Account Review stage to Manager 1 stage, the exclusiveGateway and parallelGateway records are appeared twice which leads to the creation of duplicate tasks for Manager 1. What went wrong with bpmn deployed attached here? I am using Camunda 7.11.0.
#rob2universe please find the attached xml.
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:camunda="http://camunda.org/schema/1.0/bpmn" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" id="definitions_aa944ebe-cbcd-4b68-98df-de24c78ae605" targetNamespace="http://www.omg.org/spec/BPMN/20100524/MODEL" exporter="Camunda Modeler" exporterVersion="4.12.0">
<process id="weeklyPayments" name="Weekly Payments" isExecutable="true">
<startEvent id="startEvent_0489fe56-21df-4cc0-85f3-86b8ac15f1b1" name="Weekly payments Start">
<outgoing>sequenceFlow_43dd42e8-47fc-4bb5-8f5d-387db79f3e6c</outgoing>
</startEvent>
<userTask id="payrollAccountantReviewTaskId" name="Account review" camunda:assignee="0afc00a7-1689-4003-b99f-116f7d42da17">
<incoming>sequenceFlow_43dd42e8-47fc-4bb5-8f5d-387db79f3e6c</incoming>
<incoming>sequenceFlow_dfbc5aab-c51a-41d6-9af6-03a237d29e5f</incoming>
<outgoing>sequenceFlow_f091e4f1-d246-4a3f-8cc5-d0811a4651eb</outgoing>
</userTask>
<sequenceFlow id="sequenceFlow_43dd42e8-47fc-4bb5-8f5d-387db79f3e6c" sourceRef="startEvent_0489fe56-21df-4cc0-85f3-86b8ac15f1b1" targetRef="payrollAccountantReviewTaskId" />
<exclusiveGateway id="exclusiveGatewayBeforeApproval">
<incoming>sequenceFlow_f091e4f1-d246-4a3f-8cc5-d0811a4651eb</incoming>
<outgoing>sequenceFlow_c713a794-a008-416a-811c-58be2650afaa</outgoing>
</exclusiveGateway>
<sequenceFlow id="sequenceFlow_f091e4f1-d246-4a3f-8cc5-d0811a4651eb" sourceRef="payrollAccountantReviewTaskId" targetRef="exclusiveGatewayBeforeApproval" />
<parallelGateway id="standardWorkflow_1parallelGateLevel1">
<incoming>sequenceFlow_c713a794-a008-416a-811c-58be2650afaa</incoming>
<outgoing>sequenceFlow_1b2992c2-6bbf-43a5-bd15-9bdd2a91c1de</outgoing>
</parallelGateway>
<sequenceFlow id="sequenceFlow_c713a794-a008-416a-811c-58be2650afaa" sourceRef="exclusiveGatewayBeforeApproval" targetRef="standardWorkflow_1parallelGateLevel1" />
<userTask id="userTask_8cd0a009-7d4c-4857-bcce-b0a358be9c39" name="Manager 1" camunda:assignee="165f2d43-a133-4433-8c24-219ec599a377">
<incoming>sequenceFlow_1b2992c2-6bbf-43a5-bd15-9bdd2a91c1de</incoming>
<outgoing>sequenceFlow_d578879e-ce63-4a37-96ed-ea357c63a2d0</outgoing>
</userTask>
<sequenceFlow id="sequenceFlow_1b2992c2-6bbf-43a5-bd15-9bdd2a91c1de" sourceRef="standardWorkflow_1parallelGateLevel1" targetRef="userTask_8cd0a009-7d4c-4857-bcce-b0a358be9c39" />
<exclusiveGateway id="standardWorkflow_1exclusiveGateApprovalLevel1" gatewayDirection="Diverging">
<incoming>sequenceFlow_d578879e-ce63-4a37-96ed-ea357c63a2d0</incoming>
<outgoing>sequenceFlow_dfbc5aab-c51a-41d6-9af6-03a237d29e5f</outgoing>
<outgoing>Flow_0dhem2c</outgoing>
</exclusiveGateway>
<sequenceFlow id="sequenceFlow_d578879e-ce63-4a37-96ed-ea357c63a2d0" sourceRef="userTask_8cd0a009-7d4c-4857-bcce-b0a358be9c39" targetRef="standardWorkflow_1exclusiveGateApprovalLevel1" />
<sequenceFlow id="sequenceFlow_dfbc5aab-c51a-41d6-9af6-03a237d29e5f" sourceRef="standardWorkflow_1exclusiveGateApprovalLevel1" targetRef="payrollAccountantReviewTaskId">
<conditionExpression id="conditionExpression_a0828e4f-68ba-4c1c-ab91-fe454ccd22cf">#{not approved}</conditionExpression>
</sequenceFlow>
<endEvent id="endEvent_1215456f-e1ed-4be6-bd75-e3eb7dba1a1b" name="Weekly payments Approved">
<incoming>Flow_0dhem2c</incoming>
</endEvent>
<sequenceFlow id="Flow_0dhem2c" sourceRef="standardWorkflow_1exclusiveGateApprovalLevel1" targetRef="endEvent_1215456f-e1ed-4be6-bd75-e3eb7dba1a1b" />
</process>
<bpmndi:BPMNDiagram id="BPMNDiagram_9b401e85-e737-4fc3-879a-23f2a5c74904">
<bpmndi:BPMNPlane id="BPMNPlane_3ac9827c-4875-42bb-ac8a-2e42f790c559" bpmnElement="weeklyPayments">
<bpmndi:BPMNEdge id="BPMNEdge_c7c043df-75ce-46f3-99b0-c60fecb44739" bpmnElement="sequenceFlow_dfbc5aab-c51a-41d6-9af6-03a237d29e5f">
<di:waypoint x="831" y="143" />
<di:waypoint x="831" y="270" />
<di:waypoint x="406" y="270" />
<bpmndi:BPMNLabel>
<dc:Bounds x="1343" y="243" width="34" height="14" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="BPMNEdge_96d0e27e-e6d5-4789-8594-3513310041dd" bpmnElement="sequenceFlow_d578879e-ce63-4a37-96ed-ea357c63a2d0">
<di:waypoint x="756" y="118" />
<di:waypoint x="806" y="118" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="BPMNEdge_38784eaf-da72-4325-b7d2-0cfd683f26c0" bpmnElement="sequenceFlow_1b2992c2-6bbf-43a5-bd15-9bdd2a91c1de">
<di:waypoint x="606" y="118" />
<di:waypoint x="656" y="118" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="BPMNEdge_404bebd5-39e7-4b0f-b99f-bedaf6e45cfc" bpmnElement="sequenceFlow_c713a794-a008-416a-811c-58be2650afaa">
<di:waypoint x="506" y="118" />
<di:waypoint x="556" y="118" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="BPMNEdge_13585ad2-8ee9-4257-a654-3208c36ac7eb" bpmnElement="sequenceFlow_f091e4f1-d246-4a3f-8cc5-d0811a4651eb">
<di:waypoint x="356" y="230" />
<di:waypoint x="356" y="118" />
<di:waypoint x="456" y="118" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="BPMNEdge_39143a53-8255-453b-a745-34fe234aa4e1" bpmnElement="sequenceFlow_43dd42e8-47fc-4bb5-8f5d-387db79f3e6c">
<di:waypoint x="208" y="270" />
<di:waypoint x="306" y="270" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="Flow_0dhem2c_di" bpmnElement="Flow_0dhem2c">
<di:waypoint x="856" y="118" />
<di:waypoint x="932" y="118" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNShape id="BPMNShape_2420f9d5-d6c9-4367-b4eb-5da788186a33" bpmnElement="startEvent_0489fe56-21df-4cc0-85f3-86b8ac15f1b1">
<dc:Bounds x="172" y="252" width="36" height="36" />
<bpmndi:BPMNLabel>
<dc:Bounds x="150" y="288" width="88" height="27" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="BPMNShape_d5ebb429-87d2-4cf4-b98d-c1b1c1f22402" bpmnElement="payrollAccountantReviewTaskId">
<dc:Bounds x="306" y="230" width="100" height="80" />
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="BPMNShape_877ee2fd-54e0-4c3d-8710-5b50d2e2b696" bpmnElement="exclusiveGatewayBeforeApproval" isMarkerVisible="true">
<dc:Bounds x="456" y="93" width="50" height="50" />
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="BPMNShape_02a3cde9-8508-4420-9597-ba7cf5977ed9" bpmnElement="standardWorkflow_1parallelGateLevel1">
<dc:Bounds x="556" y="93" width="50" height="50" />
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="BPMNShape_336a138c-1325-4596-a68c-364bf0951aa0" bpmnElement="userTask_8cd0a009-7d4c-4857-bcce-b0a358be9c39">
<dc:Bounds x="656" y="78" width="100" height="80" />
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="BPMNShape_11ddb890-d80a-46ec-9c67-beaaf3b5723f" bpmnElement="standardWorkflow_1exclusiveGateApprovalLevel1" isMarkerVisible="true">
<dc:Bounds x="806" y="93" width="50" height="50" />
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="BPMNShape_bca69cf4-b5e9-40a5-8271-92ff9d0c4ec0" bpmnElement="endEvent_1215456f-e1ed-4be6-bd75-e3eb7dba1a1b">
<dc:Bounds x="932" y="100" width="36" height="36" />
<bpmndi:BPMNLabel>
<dc:Bounds x="906" y="156" width="88" height="27" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNShape>
</bpmndi:BPMNPlane>
</bpmndi:BPMNDiagram>
</definitions>
Try to move the Manager 1 task on the diagram. Do you now see two sequence flows from the parallel gateway to the user task?
(if this is not the root cause, can you include the modle xml in your post?)
I'm using WiX to create a custom dialog/page in my installer, based on WixUI_Mondo. The custom dialog has edit controls, similar to this:
<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
<Fragment>
<UI>
<Dialog Id="ConfigDlg" Width="370" Height="270" Title="!(loc.SetupTypeDlg_Title)" >
<Control Id="idTxt11" Type="Text" X="20" Y="65" Width="60" Height="16" Text="Name:" />
<Control Id="idEdt11" Type="Edit" X="90" Y="60" Width="120" Height="20" Default="yes" Property="PROP_NAME" />
<Control Id="Back" Type="PushButton" X="180" Y="243" Width="56" Height="17" Text="!(loc.WixUIBack)" />
<Control Id="Next" Type="PushButton" X="236" Y="243" Width="56" Height="17" Text="!(loc.WixUINext)" />
<Control Id="Cancel" Type="PushButton" X="304" Y="243" Width="56" Height="17" Cancel="yes" Text="!(loc.WixUICancel)">
<Publish Event="SpawnDialog" Value="CancelDlg">1</Publish>
</Control>
</Dialog>
</UI>
</Fragment>
</Wix>
I can read those controls from my custom action DLL (written in C++) when the Next button is clicked, by invoking it as such:
<Publish Dialog="ConfigDlg" Control="Next" Event="DoAction" Value="idCA_NextBtn">1</Publish>
but I also need to pre-populate those edit boxes when the page is first shown (by reading these values from the registry). This may be needed if someone is upgrading or repairing my software.
The question is, how do I do that from my custom action?
For each property that you need read from the registry (for upgrades/repairs) just add a <RegistrySearch> element that populates those properties.
I'm using a custom template with views inside on a ListView, but what happens is that the click do not work. I tried to disable touchEnabled on all views inside and still nothing.
In the example below and in the attachment that I am including, there are two ListViews, one with a template with Views inside, and another ListView with a template with no Views inside.
Tested on emulator iOS 10.0.0
[index.xml]
<Alloy>
<Window class="container" layout="vertical">
<Label text="Click is not working on a template with views inside (tested iOS 10.0.0)" top="30"/>
<ListView id="list1" defaultItemTemplate="temp1" height="200" allowsSelection="false" separatorColor="transparent" top="10" onItemClick="testClick">
<Templates>
<ItemTemplate name="temp1" onClick="testClick">
<View backgroundColor="blue">
<View backgroundColor="red" width="60%" height="90%">
<Label bindId="label1"/>
</View>
</View>
</ItemTemplate>
</Templates>
<ListSection headerTitle="Click DON'T WORK!" fontSize="12">
<ListItem label1:text="01" />
<ListItem label1:text="02" />
<ListItem label1:text="03" />
</ListSection>
</ListView>
<ListView id="list2" defaultItemTemplate="temp2" height="200" allowsSelection="false" separatorColor="transparent">
<Templates>
<ItemTemplate name="temp2" onClick="testClick" >
<View backgroundColor="cyan">
</View>
</ItemTemplate>
</Templates>
<ListSection headerTitle="Click WORKS!">
<ListItem />
<ListItem />
<ListItem />
</ListSection>
</ListView>
</Window>
[index.js]
function testClick() {
alert('CLICK');
}
$.index.open();
Download the project if you need:
https://www.dropbox.com/s/t3h6mchsb0e5bdh/ListViewBugTemplateClick.zip?dl=0
You need to use onItemclick the C is lowercase, and it should work but remove this onClick<ItemTemplate name="temp1" onClick="testClick">
<ListView id="list1" defaultItemTemplate="temp1" height="200" separatorColor="transparent" top="10" onItemclick="testClick">
<Templates>
<ItemTemplate name="temp1">
<View backgroundColor="blue">
<View backgroundColor="red" width="60%" height="90%">
<Label bindId="label1"/>
</View>
</View>
</ItemTemplate>
</Templates>
<ListSection headerTitle="Click DON'T WORK!" fontSize="12">
<ListItem label1:text="01" label1:touchEnabled="false" label1:touchable="false" />
<ListItem label1:text="02"/>
<ListItem label1:text="03" />
</ListSection>
</ListView>
I have a simple bpmn with only script task that sets a process variable and a human task that accepts two input parameters, one output parameter and has defined one form data field.
After I start the process the execution stops on the human task. I'm then trying to obtain the variables of the human task form (i.e. the input variables and\or the form data field but not the execution variable set by the screen task).
The results of querying REST API are as follows:
task/id/variables - input variables and script task variable
task/id/form-variables - input variables, form data field and script task variable
task/id/localVariables - empty
I can't understand why the script task variable is returned along with other form-variables.
How can I obtain only the input variables and form data field but not the screen task variable (and possibly all other process variables)?
EDIT: I don't want to use query parameters to select variable names.
I'm using the Camunda Widlfly 10.0.0.
The bpmn I'm using:
<?xml version="1.0" encoding="UTF-8"?>
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:camunda="http://camunda.org/schema/1.0/bpmn" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="Definitions_1" targetNamespace="http://bpmn.io/schema/bpmn" exporter="Camunda Modeler" exporterVersion="1.3.0">
<bpmn:process id="userTaskExample" isExecutable="true">
<bpmn:startEvent id="StartEvent_02mu30n">
<bpmn:outgoing>SequenceFlow_14v3dyf</bpmn:outgoing>
</bpmn:startEvent>
<bpmn:endEvent id="EndEvent_144sl4n">
<bpmn:incoming>SequenceFlow_0acu0wh</bpmn:incoming>
</bpmn:endEvent>
<bpmn:sequenceFlow id="SequenceFlow_0acu0wh" sourceRef="Task_096f7n7" targetRef="EndEvent_144sl4n" />
<bpmn:userTask id="Task_096f7n7" name="user task sk">
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="form_1" label="form_1" type="string" defaultValue="form_1_" />
</camunda:formData>
<camunda:inputOutput>
<camunda:inputParameter name="input_1">input_1_val</camunda:inputParameter>
<camunda:inputParameter name="input_2">input_2_val</camunda:inputParameter>
<camunda:outputParameter name="output_1">output_2</camunda:outputParameter>
</camunda:inputOutput>
</bpmn:extensionElements>
<bpmn:incoming>SequenceFlow_0sulfwg</bpmn:incoming>
<bpmn:outgoing>SequenceFlow_0acu0wh</bpmn:outgoing>
</bpmn:userTask>
<bpmn:sequenceFlow id="SequenceFlow_14v3dyf" sourceRef="StartEvent_02mu30n" targetRef="Task_0cphzp1" />
<bpmn:sequenceFlow id="SequenceFlow_0sulfwg" sourceRef="Task_0cphzp1" targetRef="Task_096f7n7" />
<bpmn:scriptTask id="Task_0cphzp1" name="script task sk" scriptFormat="groovy" camunda:resultVariable="script_task_variable">
<bpmn:incoming>SequenceFlow_14v3dyf</bpmn:incoming>
<bpmn:outgoing>SequenceFlow_0sulfwg</bpmn:outgoing>
<bpmn:script><![CDATA["scipt task variable"]]></bpmn:script>
</bpmn:scriptTask>
</bpmn:process>
<bpmndi:BPMNDiagram id="BPMNDiagram_1">
<bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="userTaskExample">
<bpmndi:BPMNShape id="StartEvent_02mu30n_di" bpmnElement="StartEvent_02mu30n">
<dc:Bounds x="151" y="66" width="36" height="36" />
<bpmndi:BPMNLabel>
<dc:Bounds x="169" y="102" width="0" height="0" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="EndEvent_144sl4n_di" bpmnElement="EndEvent_144sl4n">
<dc:Bounds x="616" y="66" width="36" height="36" />
<bpmndi:BPMNLabel>
<dc:Bounds x="634" y="102" width="0" height="0" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNShape>
<bpmndi:BPMNEdge id="SequenceFlow_0acu0wh_di" bpmnElement="SequenceFlow_0acu0wh">
<di:waypoint xsi:type="dc:Point" x="433" y="84" />
<di:waypoint xsi:type="dc:Point" x="524" y="84" />
<di:waypoint xsi:type="dc:Point" x="524" y="84" />
<di:waypoint xsi:type="dc:Point" x="616" y="84" />
<bpmndi:BPMNLabel>
<dc:Bounds x="539" y="84" width="0" height="0" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNEdge>
<bpmndi:BPMNShape id="UserTask_1lppvq8_di" bpmnElement="Task_096f7n7">
<dc:Bounds x="333" y="44" width="100" height="80" />
</bpmndi:BPMNShape>
<bpmndi:BPMNEdge id="SequenceFlow_14v3dyf_di" bpmnElement="SequenceFlow_14v3dyf">
<di:waypoint xsi:type="dc:Point" x="169" y="102" />
<di:waypoint xsi:type="dc:Point" x="169" y="133" />
<di:waypoint xsi:type="dc:Point" x="252" y="133" />
<di:waypoint xsi:type="dc:Point" x="192" y="204" />
<di:waypoint xsi:type="dc:Point" x="275" y="204" />
<di:waypoint xsi:type="dc:Point" x="275" y="284" />
<bpmndi:BPMNLabel>
<dc:Bounds x="222" y="153.5" width="0" height="0" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="SequenceFlow_0sulfwg_di" bpmnElement="SequenceFlow_0sulfwg">
<di:waypoint xsi:type="dc:Point" x="325" y="331" />
<di:waypoint xsi:type="dc:Point" x="401" y="342" />
<di:waypoint xsi:type="dc:Point" x="383" y="204" />
<di:waypoint xsi:type="dc:Point" x="383" y="124" />
<bpmndi:BPMNLabel>
<dc:Bounds x="392" y="258" width="0" height="0" />
</bpmndi:BPMNLabel>
</bpmndi:BPMNEdge>
<bpmndi:BPMNShape id="ScriptTask_1q3eqsu_di" bpmnElement="Task_0cphzp1">
<dc:Bounds x="225" y="284" width="100" height="80" />
</bpmndi:BPMNShape>
</bpmndi:BPMNPlane>
</bpmndi:BPMNDiagram>
</bpmn:definitions>
Your results suggest you are displaying the variable defined in the script task in the human task form.
I say this because when you look at the source to retrieve the form variables we see:
// first, evaluate form fields
TaskDefinition taskDefinition = task.getTaskDefinition();
if (taskDefinition != null) {
TaskFormData taskFormData = taskDefinition.getTaskFormHandler().createTaskForm(task);
for (FormField formField : taskFormData.getFormFields()) {
if(formVariableNames == null || formVariableNames.contains(formField.getId())) {
result.put(formField.getId(), createVariable(formField, task));
}
}
}
// collect remaining variables from task scope and parent scopes
task.collectVariables(result, formVariableNames, false, deserializeObjectValues);
Notice we ierate over the form field definition to retrieve the variable names we care about, then we populate the data from the execution context.
Ultimately Activiti/Camunda (they are 90% the same at the engine level) does no differentiate between data entered in a form and data created in a script or service task (e.g. as a result variable).
If you need to separate these for some reason, I suggest you use a naming convention and query process variables based on the variable name convention.
I’m facing this strange behavior for some of my WiX-based installers. After installation, if I try to remove via Add Remove Program (Programs and Features in Windows 7) using Right Click Menu and select Uninstall (This default BTW), it only shows a progress dialog which quits immediately and program never uninstalls and stays intact.
The Same behavior is there upon using
msiexec /x {ProductCode}
(or Product.msi)
However, using Right Click Menu, select Change and then from Maintenance Dialog Box, select Remove, uninstalls it perfectly.
Here is the code for InstallUISequence and InstallExecuteSequence:
<InstallUISequence>
<Custom Before="CostFinalize" Action="CheckPreReqs" />
<Show Dialog="MaintenanceWelcomeDlg"
Overridable="yes"
Sequence="1230">Installed And Not RESUME And Not Preselected And Not PATCH</Show>
</InstallUISequence>
<InstallExecuteSequence>
<ScheduleReboot Sequence="6410">ISSCHEDULEREBOOT</ScheduleReboot>
<LaunchConditions Sequence="410">Not Installed</LaunchConditions>
<FindRelatedProducts Sequence="420">NOT ISSETUPDRIVEN</FindRelatedProducts>
<AppSearch Sequence="400" />
<CCPSearch Sequence="500">CCP_TEST</CCPSearch>
<RMCCPSearch Sequence="600">Not CCP_SUCCESS And CCP_TEST</RMCCPSearch>
<ValidateProductID Sequence="700" />
<CostInitialize Sequence="800" />
<FileCost Sequence="900" />
<IsolateComponents Sequence="950" />
<CostFinalize Sequence="1000" />
<SetODBCFolders Sequence="1100" />
<MigrateFeatureStates Sequence="1200" />
<InstallValidate Sequence="1400" />
<InstallInitialize Sequence="1501" />
<AllocateRegistrySpace Sequence="1550">NOT Installed</AllocateRegistrySpace>
<ProcessComponents Sequence="1600" />
<UnpublishComponents Sequence="1700" />
<UnpublishFeatures Sequence="1800" />
<StopServices Sequence="1900">VersionNT</StopServices>
<DeleteServices Sequence="2000">VersionNT</DeleteServices>
<UnregisterComPlus Sequence="2100" />
<SelfUnregModules Sequence="2200" />
<UnregisterTypeLibraries Sequence="2300" />
<RemoveODBC Sequence="2400" />
<UnregisterFonts Sequence="2500" />
<RemoveRegistryValues Sequence="2600" />
<UnregisterClassInfo Sequence="2700" />
<UnregisterExtensionInfo Sequence="2800" />
<UnregisterProgIdInfo Sequence="2900" />
<UnregisterMIMEInfo Sequence="3000" />
<RemoveIniValues Sequence="3100" />
<RemoveShortcuts Sequence="3200" />
<RemoveEnvironmentStrings Sequence="3300" />
<RemoveDuplicateFiles Sequence="3400" />
<RemoveFiles Sequence="3500" />
<RemoveFolders Sequence="3600" />
<CreateFolders Sequence="3700" />
<MoveFiles Sequence="3800" />
<InstallFiles Sequence="4000" />
<DuplicateFiles Sequence="4210" />
<PatchFiles Sequence="4090" />
<BindImage Sequence="4300" />
<CreateShortcuts Sequence="4500" />
<RegisterClassInfo Sequence="4600" />
<RegisterExtensionInfo Sequence="4700" />
<RegisterProgIdInfo Sequence="4800" />
<RegisterMIMEInfo Sequence="4900" />
<WriteRegistryValues Sequence="5000" />
<WriteIniValues Sequence="5100" />
<WriteEnvironmentStrings Sequence="5200" />
<RegisterFonts Sequence="5300" />
<InstallODBC Sequence="5400" />
<RegisterTypeLibraries Sequence="5500" />
<SelfRegModules Sequence="5600" />
<RegisterComPlus Sequence="5700" />
<InstallServices Sequence="5800">VersionNT</InstallServices>
<StartServices Sequence="5900">VersionNT</StartServices>
<RegisterUser Sequence="6000" />
<RegisterProduct Sequence="6100" />
<PublishComponents Sequence="6200" />
<PublishFeatures Sequence="6300" />
<PublishProduct Sequence="6400" />
<InstallFinalize Sequence="6600" />
<RemoveExistingProducts Sequence="1410" />
<MsiPublishAssemblies Sequence="6250" />
<MsiUnpublishAssemblies Sequence="1750" />
</InstallExecuteSequence>
How do I fix this problem?
Chances are that you are attempting to do "stuff" during the InstallUISequence (which doesn't display from ARP or msiexec /x) and you are (incorrectly) requiring a User Interface and performing steps here, as opposed to performing them during the InstallExecuteSequence
If you inspect the two sequences using Orca, you should be able to identify the problematic actions.