It is possible that the review fails or the advertiser rejects the work, which will involve the process of repeated revision, submission and review of the work. Therefore executive email list, how to deal with this complex process in a simple and clear way is the focus of my work. This project involves 6 key nodes: script submission, script confirmation, work submission, work review, executive email list work confirmation, and work release. There is a waiting period between every two nodes. I once considered using the method in the Jingdong case to add a "half node" that "wait for XX" between the two nodes, but I felt that this would complicate the process and increase the user's cognitive cost, so I gave up.
In addition, among the 6 nodes, in the stages of "script confirmation", "work review" and "work confirmation", there may be failures, and then repeated revisions, that is, there executive email list will be a state cycle. For example: from "script pending confirmation" to "script rejected", then resubmitted the script, and then changed to "script pending confirmation". My final approach is to treat each executive email list node as a "phase" to which all states related to a node are located. Instead, as in some other cases, a node's transaction is completed before targeting this node.
That is to say, I clearly inform the user which node needs to be concerned at the moment, so that the user can form the cognition of "after processing all the transactions of this node, you can enter the next node". In the step bar, I used the change of the step name to reinforce the user executive email list's perception of the current state: In steps 2, 4, and 5, there may be failures, resubmit, and then wait for the cyclic process of confirmation/audit. Taking step 2 as an example, in my solution executive email list, the user is provided with an entry to resubmit the script after "the script is rejected". After the user completes the resubmission of the script in this state, it will directly become "script pending confirmation", and will no longer go through the "script submission" node.