Using Status Previous or any other Previous fields in the site-defined macro, the corresponding event is not triggered from the secondary/application servers. It works from Background/Primary servers.
Release : 17.3
In an event and macro, the call goes to an animator to trigger the event. In the case of the Primary server SDM user interface, when the Previous field is changed from field1 to field2 the operation happens w.r.t Primary domsrvr and Primary domsrvr keeps track of the previous attribute. An event gets created and fired by an animator. The animator sends the call to primary domsrvr(because the animator which resides on primary is tied up with primary domsrvr) and since primary domsrvr knows the prev attribute the macro execution will be true.
In the case of the Application server, when the previous field is changed from field1 to field2, the operation happens w.r.t Application domsrvr and Application domsrvr keeps track of the prev attribute. An event gets created and is fired by the animator. The animator sends the call to Primary domsrvr(because the animator which resides on Primary is tied up with Primary domsrvr) and since Primary domsrvr doesn't know the prev attribute the macro execution result will be false.
We have limitations in regards to Previous fields.