How to decide what happens and is not saved in the workflow

I have a question about saving state values ​​in a constant workflow. I have two properties inside one of my extension classes:

    public int ApprovalCount
    {
        get;
        set;
    }

    public bool ApprovedByAllInitialApprovers
    {
        get;
        set;
    }

These properties are set during some calculations that are performed using a different method.

My problem is that when the workflow is idle and saved, the state of these values ​​is also stored in the database, so if I call the method again in my extension class, I collect the values ​​when I left them; I understand that this behavior, of course, is fundamental to how work processes work in a constant mode, and in 90% of cases I want values ​​to be remembered and preserved, but what about exceptions? Is there a way to “mark” a property (possibly with an attribute) to indicate that I do not want it to be saved? Or should I just reset the values ​​before I perform my calculations every time?

Any help is greatly appreciated. Thanks in advance.

+3
source share
1 answer

.

  • , , . , , , NonSerialized.
  • , - , . , , .
0

All Articles