Mixing
Content in an embedded form textarea not being set to a process variable
Within a user task, the embedded form markup is
...
<div class="form-group">
<textarea class="form-control"
cam-variable-name="jobDescription"
cam-variable-type="String"
name="jobDescription">
</textarea>
</div>
...
There is a process variable jobDescription that has been set - this has been verified via the Tomcat logs.
The problem is that content of the textarea is not being set to that of the process variable.
Camunda 7.10 is being used and I have checked the Camunda manual 7.10
If the textarea is changed to input type="text", this shows the correct content.
camunda
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
add a comment |
Within a user task, the embedded form markup is
...
<div class="form-group">
<textarea class="form-control"
cam-variable-name="jobDescription"
cam-variable-type="String"
name="jobDescription">
</textarea>
</div>
...
There is a process variable jobDescription that has been set - this has been verified via the Tomcat logs.
The problem is that content of the textarea is not being set to that of the process variable.
Camunda 7.10 is being used and I have checked the Camunda manual 7.10
If the textarea is changed to input type="text", this shows the correct content.
camunda
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
seems you are using it exactly as documented: docs.camunda.org/manual/7.6/reference/embedded-forms/controls/… ... maybe worth filing a bug-issue?
– Jan Galinski
Jan 7 at 14:18
add a comment |
Within a user task, the embedded form markup is
...
<div class="form-group">
<textarea class="form-control"
cam-variable-name="jobDescription"
cam-variable-type="String"
name="jobDescription">
</textarea>
</div>
...
There is a process variable jobDescription that has been set - this has been verified via the Tomcat logs.
The problem is that content of the textarea is not being set to that of the process variable.
Camunda 7.10 is being used and I have checked the Camunda manual 7.10
If the textarea is changed to input type="text", this shows the correct content.
camunda
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
Within a user task, the embedded form markup is
...
<div class="form-group">
<textarea class="form-control"
cam-variable-name="jobDescription"
cam-variable-type="String"
name="jobDescription">
</textarea>
</div>
...
There is a process variable jobDescription that has been set - this has been verified via the Tomcat logs.
The problem is that content of the textarea is not being set to that of the process variable.
Camunda 7.10 is being used and I have checked the Camunda manual 7.10
If the textarea is changed to input type="text", this shows the correct content.
camunda
camunda
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
edited Jan 7 at 14:54
Kevin Swann
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
asked Jan 2 at 10:50
Kevin SwannKevin Swann
543621
543621
seems you are using it exactly as documented: docs.camunda.org/manual/7.6/reference/embedded-forms/controls/… ... maybe worth filing a bug-issue?
– Jan Galinski
Jan 7 at 14:18
add a comment |
seems you are using it exactly as documented: docs.camunda.org/manual/7.6/reference/embedded-forms/controls/… ... maybe worth filing a bug-issue?
– Jan Galinski
Jan 7 at 14:18
seems you are using it exactly as documented: docs.camunda.org/manual/7.6/reference/embedded-forms/controls/… ... maybe worth filing a bug-issue?
– Jan Galinski
Jan 7 at 14:18
seems you are using it exactly as documented: docs.camunda.org/manual/7.6/reference/embedded-forms/controls/… ... maybe worth filing a bug-issue?
– Jan Galinski
Jan 7 at 14:18
add a comment |
1 Answer
1
active
oldest
votes
This works for Camunda 7.10.
To populate a textarea, the form needs to use the Camunda form events
<script cam-script type="text/form-script">
var variableManager = camForm.variableManager;
var jobRequestInfo = $scope.jobRequestInfo = {};
var jobDescription = $scope.jobDescription = {};
camForm.on( 'form-loaded', function() {
camForm.variableManager.fetchVariable( 'jobRequestInfo' );
camForm.variableManager.fetchVariable( 'jobDescription' );
});
camForm.on( 'variables-fetched', function() {
$scope.jobRequestInfo = camForm.variableManager.variable( 'jobRequestInfo' ).value;
$scope.jobDescription = camForm.variableManager.variable( 'jobDescription' ).value;
});
camForm.on( 'variables-applied', function() {
$( '[name="jobDescription"]' ).val( $scope.jobDescription );
});
camForm.on( 'submit', function( ev ) {
;
});
</script>
...
<div class="form-group">
<label for="jobDescription">Job Description</label>
<textarea class="form-control"
ng-model="jobRequestInfo.description"
name="jobDescription"
rows="20">
</textarea>
</div>
...
There are two process-scoped variables:
jobDescriptionaStringthat is populated with the initial value.
jobRequestInfoa POJO with a fielddescriptionthat is populated with the final, edited value.
Note that Camunda does not fully support all HTML types such as radio buttons so beyond basic forms, using the Camunda form events is usually necessary.
Also, using Angular integration and POJO variables, as above, allows a significant reduction in process variables.
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54004990%2fcontent-in-an-embedded-form-textarea-not-being-set-to-a-process-variable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This works for Camunda 7.10.
To populate a textarea, the form needs to use the Camunda form events
<script cam-script type="text/form-script">
var variableManager = camForm.variableManager;
var jobRequestInfo = $scope.jobRequestInfo = {};
var jobDescription = $scope.jobDescription = {};
camForm.on( 'form-loaded', function() {
camForm.variableManager.fetchVariable( 'jobRequestInfo' );
camForm.variableManager.fetchVariable( 'jobDescription' );
});
camForm.on( 'variables-fetched', function() {
$scope.jobRequestInfo = camForm.variableManager.variable( 'jobRequestInfo' ).value;
$scope.jobDescription = camForm.variableManager.variable( 'jobDescription' ).value;
});
camForm.on( 'variables-applied', function() {
$( '[name="jobDescription"]' ).val( $scope.jobDescription );
});
camForm.on( 'submit', function( ev ) {
;
});
</script>
...
<div class="form-group">
<label for="jobDescription">Job Description</label>
<textarea class="form-control"
ng-model="jobRequestInfo.description"
name="jobDescription"
rows="20">
</textarea>
</div>
...
There are two process-scoped variables:
jobDescriptionaStringthat is populated with the initial value.
jobRequestInfoa POJO with a fielddescriptionthat is populated with the final, edited value.
Note that Camunda does not fully support all HTML types such as radio buttons so beyond basic forms, using the Camunda form events is usually necessary.
Also, using Angular integration and POJO variables, as above, allows a significant reduction in process variables.
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
add a comment |
This works for Camunda 7.10.
To populate a textarea, the form needs to use the Camunda form events
<script cam-script type="text/form-script">
var variableManager = camForm.variableManager;
var jobRequestInfo = $scope.jobRequestInfo = {};
var jobDescription = $scope.jobDescription = {};
camForm.on( 'form-loaded', function() {
camForm.variableManager.fetchVariable( 'jobRequestInfo' );
camForm.variableManager.fetchVariable( 'jobDescription' );
});
camForm.on( 'variables-fetched', function() {
$scope.jobRequestInfo = camForm.variableManager.variable( 'jobRequestInfo' ).value;
$scope.jobDescription = camForm.variableManager.variable( 'jobDescription' ).value;
});
camForm.on( 'variables-applied', function() {
$( '[name="jobDescription"]' ).val( $scope.jobDescription );
});
camForm.on( 'submit', function( ev ) {
;
});
</script>
...
<div class="form-group">
<label for="jobDescription">Job Description</label>
<textarea class="form-control"
ng-model="jobRequestInfo.description"
name="jobDescription"
rows="20">
</textarea>
</div>
...
There are two process-scoped variables:
jobDescriptionaStringthat is populated with the initial value.
jobRequestInfoa POJO with a fielddescriptionthat is populated with the final, edited value.
Note that Camunda does not fully support all HTML types such as radio buttons so beyond basic forms, using the Camunda form events is usually necessary.
Also, using Angular integration and POJO variables, as above, allows a significant reduction in process variables.
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
add a comment |
This works for Camunda 7.10.
To populate a textarea, the form needs to use the Camunda form events
<script cam-script type="text/form-script">
var variableManager = camForm.variableManager;
var jobRequestInfo = $scope.jobRequestInfo = {};
var jobDescription = $scope.jobDescription = {};
camForm.on( 'form-loaded', function() {
camForm.variableManager.fetchVariable( 'jobRequestInfo' );
camForm.variableManager.fetchVariable( 'jobDescription' );
});
camForm.on( 'variables-fetched', function() {
$scope.jobRequestInfo = camForm.variableManager.variable( 'jobRequestInfo' ).value;
$scope.jobDescription = camForm.variableManager.variable( 'jobDescription' ).value;
});
camForm.on( 'variables-applied', function() {
$( '[name="jobDescription"]' ).val( $scope.jobDescription );
});
camForm.on( 'submit', function( ev ) {
;
});
</script>
...
<div class="form-group">
<label for="jobDescription">Job Description</label>
<textarea class="form-control"
ng-model="jobRequestInfo.description"
name="jobDescription"
rows="20">
</textarea>
</div>
...
There are two process-scoped variables:
jobDescriptionaStringthat is populated with the initial value.
jobRequestInfoa POJO with a fielddescriptionthat is populated with the final, edited value.
Note that Camunda does not fully support all HTML types such as radio buttons so beyond basic forms, using the Camunda form events is usually necessary.
Also, using Angular integration and POJO variables, as above, allows a significant reduction in process variables.
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
This works for Camunda 7.10.
To populate a textarea, the form needs to use the Camunda form events
<script cam-script type="text/form-script">
var variableManager = camForm.variableManager;
var jobRequestInfo = $scope.jobRequestInfo = {};
var jobDescription = $scope.jobDescription = {};
camForm.on( 'form-loaded', function() {
camForm.variableManager.fetchVariable( 'jobRequestInfo' );
camForm.variableManager.fetchVariable( 'jobDescription' );
});
camForm.on( 'variables-fetched', function() {
$scope.jobRequestInfo = camForm.variableManager.variable( 'jobRequestInfo' ).value;
$scope.jobDescription = camForm.variableManager.variable( 'jobDescription' ).value;
});
camForm.on( 'variables-applied', function() {
$( '[name="jobDescription"]' ).val( $scope.jobDescription );
});
camForm.on( 'submit', function( ev ) {
;
});
</script>
...
<div class="form-group">
<label for="jobDescription">Job Description</label>
<textarea class="form-control"
ng-model="jobRequestInfo.description"
name="jobDescription"
rows="20">
</textarea>
</div>
...
There are two process-scoped variables:
jobDescriptionaStringthat is populated with the initial value.
jobRequestInfoa POJO with a fielddescriptionthat is populated with the final, edited value.
Note that Camunda does not fully support all HTML types such as radio buttons so beyond basic forms, using the Camunda form events is usually necessary.
Also, using Angular integration and POJO variables, as above, allows a significant reduction in process variables.
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
answered Feb 6 at 11:19
Kevin SwannKevin Swann
543621
543621
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54004990%2fcontent-in-an-embedded-form-textarea-not-being-set-to-a-process-variable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
seems you are using it exactly as documented: docs.camunda.org/manual/7.6/reference/embedded-forms/controls/… ... maybe worth filing a bug-issue?
– Jan Galinski
Jan 7 at 14:18