by Variance InfoTech Pvt Ltd

Conditional Notification trigger an notifications on the screen and also prevent record from being saved depending on condition mentioned in the Conditional Notification Settings. It also works on detail view of particular module’s record. It also supports on duplicate record.

Free 30 day trial
Try it Now

#1582 - FIelds do not appear in field list on Conditions

Closed Bug? created by mtierno 5 years ago

Hello! I've created several custom fields on Opportunities module. Some of them are in the edit view, some are not.

When I try to create a Conditional Notification, when creating a new Condition, only the fields on the Edit View appear.I've tested. If I put the field on Edit View, it appears in the Condition list. Is I remove the field from the Edit View, the field won't appear in the Condition list.

The point is that I have some control fields which I change the value using workflows. They shold not appear to the user, but they are crucial for a certain Conditional Notification I want to implement.

Is this behavior planned by you guys or is it a bug?

In any case, how do I fix or change this behavior?

Thanks in advance

Marcio

  1. varianceinfotech member avatar

    Variance InfoTech Pvt Ltd Provider

    5 years ago

    Hello Marcio,

    Currently We have consider only Editview fields in condition block part because Conditional Notification trigger when any action taken in editview and also in detail view if condition matched.

    Can you please tell us your control fields display in detail view or not ?

    Regards, Variance Infotech PVT LTD

    • mtierno member avatar

      mtierno

      5 years ago

      Theo Control fields should not appear in edit view.

      For clarification, I use a condition with a regular field appearing in Edit View AND a condition with a hidden field on a Prevent Save CN.

      Your add on would be far more powerful If you guys allow hidden fields to be user on conditions.

      In my particular case, in Module Opportunities, when an opp is closes (won or lost), I change the value of custom field closed_c to 1 via Workflow. Then a Prevent Save CN with a condition closed_c=1 will avoid any changes on a previously closed opp. Really useful.

      With the current restriction in your product, I am gonna need to code in PHP... So many other needs described in the Forum could be addressed with a Workflow/CN combo!!!!

    • varianceinfotech member avatar

      Variance InfoTech Pvt Ltd Provider

      5 years ago

      OK Thanks for your suggestions and feedback.

      We will review and come back

    • varianceinfotech member avatar

      Variance InfoTech Pvt Ltd Provider

      5 years ago

      Hello,

      I have one question.

      Hidden field means you have added hidden field in form and you want to Prevent Save CN. Am i understanc right?

    • mtierno member avatar

      mtierno

      5 years ago

      Bye hidden field I mean a field that is not on the form. I am getting the bran field list.

  2. mtierno member avatar

    mtierno

    5 years ago

    Hello! I've done the changes by my own. It now works for any bean field - just changed the request for the form data by a bean with ID coming from $_REQUEST['record']. But if you guys intend to implement this feature out of the box, please let me know.

  3. varianceinfotech member avatar

    Variance InfoTech Pvt Ltd Provider

    4 years ago

    Hello,

    Please let us know if you have any more questions on this ticket. If not then we will close this ticket.

    Regards, Variance Infotech PVT LTD

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...