IBM RegTech Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

 

note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

Include/exclude fields from bulk update in TFUI & do not force update of controller fields

  1. Please allow for configuration of which fields within an object can be bulk updated. This way, bulk update can honor the fields that are editable in a task view.

  2. Please do not force update/selection of controller fields. I understand why you would be forced to update dependent fields if you are bulk updating controller fields, but it does not make sense that when bulk updating a dependent field, you need to update a controller field. For example, on risks, our users need to select an Action, "Accept", "Mitigate", "Transfer" or "Avoid". The actions they have available are dependent on the Risk Ranking on the risk. For example, Accept is not available if the Risk Ranking is High. It makes sense that if you bulk updated the Risk Ranking, you would need to clear out or bulk update the Actions, since they might not be valid for the updated controller Risk Ranking field. However, if you are bulk updating the Action to mark risks as "Mitigate", you should not need to update the Controller Risk Ranking field (which, like many Controller fields, is a read only field in the Risk Task View and users should not be able to update via bulk update, per point 1.)

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 14 2020
  • Future Consideration
Component End User UI
Priority Medium - Important
  • Attach files
  • Admin
    JOHN Lundgren commented
    13 Aug 21:46

    Thank you again for submitting this Idea!

    This request will not be delivered within the release currently under development, but the theme is aligned with our multi-year strategy. IBM is soliciting RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    07 May 22:24

    I think this is partially a bug. If you are trying to clear a field using bulk update, but it has a blank controller field, this is impossible. If you select "clear" on the controller field, then you lose the ability to make any updates to the dependent field.

  • Admin
    JOHN Lundgren commented
    21 Apr 19:03

    Thank you for submitting this Idea!

    The IBM team is evaluating this enhancement request. A decision or request for more information will be provided within 90 days.