Timer configuration to run quarterly

Hi Priyanka,
           1)The process runs after the completion of 3 months.
           2)The interval start time doesn't get effected upon saving and publishing process.
           Note: If we import the process model object in another environment, the process runs automatically irrespective of scheduled time.

The process model runs immediately after import in another environment irrespective of scheduled time for the first time. Later onwards, based on the condition it runs

Lakshmi,
If I save and publish the process model now Dec 22, it will trigger one task now Dec 22 and please clarify when will be the trigger date after completion of 3 months from now . Ideally I want it to run on 22nd April ,22nd July, 22nd Oct,22nd Jan.

So Lakshmi, when does the timer trigger the process when 22nd of every 3 months is given. Am still not clear.. Please elaborate

I got your point
With your specified logic, it will start the process in the first occurance of specified date and it repeats for every 3 months.But this does not satisfy in which month it has to be scheduled.
So, we can make use of advanced option as below:

Thank you Lakshmi ! A few more clarification needed :-)
1.In the screenshot , monthly interval of every 1 month is given in place of every 3 months , so should I change its value ?
2. contains(month(now(), {4,7,10,1}) condition runs for one of the values right 4,7,10,1 .

You need not do any modification for that.
As an OOTB functionality, we cannot specify the exact month to start the scheduling.
So we may go with this approach where the process runs every month and checks if that month is in the list of months specified and gets executed if the condition is satisfied.

The simplest solution is to run it every month with a simple XOR to validate that it should be run this month like you stated above. Also note that when you migrate this model, it will automatically run. So if you'd like to prevent that, use a Boolean constant flag within your gateway that is set to false until post deployment configuration.

Hi,

As per my knowledge if we do configuration like start every month and check in XOR to proceed farther will run process model every month and create instances every month which is not a better idea because we should not run unnecessary instances.
So going for the solution which was given by Subhashini is proper and even as told by practitioner, when ever we migrate this process model it will start irrespective of configured timer so yes its good to have a Boolean flag but I think the condition given in 'timer condition' will handle that.