I have process as shown below.
Simple Process
Here I have two task i.e., Draft and Review.(fig1)
In draft i have outcomes as "save & submit".
When i click on save the draft task should display in read only mode so for this i have created the new task as Draft view using display value pallet element(fig 2), in the draft view i have again outcome like edit, submit.
when i click on edit again it moves to draft task. The thing is here i have created the new task for draft view. As this is simple process i can create but for complex project it requires me to create one extra task.
And for the review also i have review view task.
In activiti there is save button is provided, but here if i click on save button it will be in edit mode not in the view mode. And for view mode i have different outcomes for example: edit and submit, when i click on edit outcome again the task should open in edit mode(should show outcomes save and submit). The submit always move to next task.
Please Can anyone provide me the solution to avoid creating the task as draft view and review view.
Thanks & Regards
Amruta Wandakar
Instead of relying on the OOTB buttons create your custom buttons "save" turns your form to read-only, and "edit" makes it writable. you find examples on creating custom form fields in activiti. if you are using activiti embedded in Alfresco you can customize your task definition (model) to include buttons and then register onClick listeners using js
Related
I am new on java and javafx. I made a simple application on javafx using mvc pattern. This application handles a person table and is structured in this way.
Model containing the persons data
View containing a menu
View containing the tableview of the persons, the detail of the selected person and three buttons (New --> add new person, Edit --> change a person, Delete --> cancel a person
View that allows to change contents of the selected person
All works fine, but I have a problem with the menu. I would like to handle the menuitem 'Save' changing the 'Disable' flag in the way that it set to 'false' or 'true' programmatically, depending on if the user changed the data or not, but I do not know how can pass it from a scene to another.
I have been searching a lot on this web site and on other sites without any result.
I have found a question on stackoverflow called 'Toggle enable/disable on Menuitem javafx from another scene?' that probably could solve my question, but unfortunately I did not understand the solution.
Is there somebody who can help me?
Thank you in advance.
Alberto
I have form in getcmsfields_forpopup for backend(admin panel) in silverstrip. In that form, I have added nested dataobjectmanager field to enter multiple dates(has_many relation). When main form open in popup window and I click on add date link, then second popup form open in the same window not in separate one. That means after entering date data and saving it, when I click on close button, whole form is closed rather going back to main form. Please help in this regard.
This can't be done using SilverStripe's default popup form unless, maybe, you extended the DataObject Manager field and had it render itself in an iFrame.
The best option would be to manage your parent DataObjects with DataObjectManger as well. DataObjectManager supports nested DataObjectManager fields. See this tutorial "Nested DataObjectManager" (on YouTube).
If you're able, can I suggest that you try out SilverStripe 3.0? The support for this kind of thing is much better in SilverStripe 3.0 than it is in 2.4.
I followed the instructions in this link
but I face a strange problem which is when the lookup is populated with the new filtered view the add button is getting disabled when I select a record from the new view !!
I debugged the code in the lookupinfo.aspx page and I found this line of code that controls whether the add button is enabled or disabled
btnAdd.disabled = (crmGrid.InnerGrid.SelectedRecords.length == 0);
and this line of code always return true despite there is a selected record !!
Can anyone help me ?
Thank you.
I followed the instructions in this link
Which link? I can't see one referenced in your question. I'll make some assumptions about what you are trying to do. I will assume that you are trying to hide an "Add Existing" button linked to a form's sub-grid. I'll also assuem you're trying to edit XML files by hand (which is the hard way!).
The easiest way to apply rules to buttons in CRM 2011 is to use Erik Pool's brilliant tool "Visual Ribbon Editor" (available here)).
To hide an "Add Existing" button based on selected records, you would:
Connect the tool to your CRM environment
Open the "parent" entity (i.e. the record type that shows the "Add Existing xxxx" button
Select the Ribbon Type to be "Sub-Grid"
Select the button you wish to manipulate
Add or edit the Enable Rules for that button
If I'm not describing a solution to your problem, maybe enhance your question - it's hard to understand what you are trying to acheive.
I'm making a small application that represents a to-do list.
The list is stored in a cusom model (derived from QAbstractItemModel) and is displayed in a QTableView.
I have also a custom widget (TaskDialog) that is used to browse and edit tasks from the list. The children of the TaskDialog are mapped to the model with a QDataWidgetMMapper.
On the task dialog I have also buttons that allow browsing through all the tasks in my to-do list (QDataWidgetMapper::toPrevious() ...).
The problem is that if I'm editing a task in the TaskDialog (e.g. the tasks name) and then browse to another task, the new edited enty isn't set in the model.
But if I edit something in the TaskDialog, then first change the focus to an other child widget of the TaskDialog and then press one of the browsing button, than the changes are written to the model.
How can I achive that widgets that are in a editing mode are accepted and written to the model.
I also tried the example of QDataWidgetMapper from Nokia. There it works perfectly. But they use a QStandardItemModel.
Best regards
Luke
I found a solution:
The submit policy of the QDataWidgetMapper has to be set to QDataWidgetMapper::ManualSubmit.
Then allways when I browse to a new item (i.e. one of the browse buttons is pressed) i submit the changes with QDataWidgetMapper::submit().
This is a question on edit form UI for a WP7 app:
I currently have my edit form fields set to 2-way binding which means that as the user changes them they save on edit and update the UI in the ViewModel (Method 1). So I don't need a Save button and there is no Cancel button (unless you code in logic to store the original state and rollback on cancel).
Method 2 would be to use 1 way binding and UpdateSource on the save button and then you could have a Cancel button which functions like the Back button (goes back without saving).
Method 1 is nice as it handles preservation of state if the app is tombstoned - WP7 will restore the page and your changes will have been saved. The downside is that there is no way for the user to restore it to it's starting state once they make changes. My form is trivial so I do not think this is a problem. The Back button acts as Go Back.
I also do calculations in the setter property in my VM that need to be reflected to the UI (ie you will in Field 1 and Field 2 is double the value (but they can also override it) - I use 2 way binding on Field 1 and update field 1 and 2 on edit. I can't think of a way to do this using explicit updating.
The problem is that I have a Delete button for the record, so when I use Method 1 with no Save and Cancel button the user is likely to click the Delete button as it is the only available option (they need to click on the Back button to go back).
My question is; should a simple form have a Save and Cancel button and commit the data only on Save, or is it ok to use 2 way binding and have no buttons?
Parts of this are mentioned in the UI Design and Interaction Guide page 68.
Changes to Application Settings should be immediately implemented. This
means that a “Done”, “OK”, or other confirming dialog is not needed.
...
If a task cannot be undone, always provide the user with an option to cancel. Text entry is an example.
Actions that overwrite or delete data, or are irreversable must have a “Cancel” button.
As for your situation you will need a confirmation for the delete action (see the ie settings for an example). For your other fields check the guide as other issues are mentioned and you could also see how the built-in settings work.
If it is possible that the user may ever not want to have their entered text changed it'll be easier to have a one-way binding and update the saved value only when the user specifically says to.
Yes, this can make the preservation of entered data slightly harder during tombstoning but means that it's easier fro the user to be able to change their mind.
In your situation, I'd recommend having on screen buttons for Save and Delete (and relying on the hardward back button for cancel).