Create Campaign API Call - creating campaign with default date

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Usually when using the API to call Create Campaign we were leaving the deadline blank so that my team is able to set the deadline when the campaign is kicked off. It looks like that functionality has changed where it is now defaulting to 2 weeks without the ability to change this date. Is it possible to set something in the Create Campaign Call to ensure that the deadline is selected upon activation via UI?

2

Sean,

Are you able to give us the most accurate dates you’re aware of when that API did nothing and then when it defaulted to two weeks?

3

I believe this functionality changed May 1st/May 2nd where deadline is now defaulting to 2 weeks.

4

I’ve just shared this with our Product team. I’ll let you know when I get an answer back :slight_smile:

5

Hi @Seanramjit1 ,
I have been looking into this, and I have some (delivery date unknown) good news for this!

if memory serves, beta/campaigns originally defaulted to 14d if there was no Deadline set. (if Deadline, deadline. if not, 14d)

When we released the “Ask during activation” feature, this changed to (if Deadline, deadline. if not, Prompt)

this past week, a change was put in to return to that original functionality (default deadline) to try to allow for our Workflows feature to seamlessly see a trigger scenario, create a campaign if required, and automatically Activate the resultant campaign.

this interrupted other customer use cases, and is being re-evaluated. I believe the are most likely going to roll back the change, and restore “Prompt for deadline upon activation”.

in the longer term, I believe the design intent was to support BOTH options:
if there is a Deadline set, thats the deadline.
if not, something to allow relative dates (deadlineDuration? much like the campaignTemplate endpoints. something like “p14d” to set a 14day deadline)
if there is no deadline or deadlineDuration == Prompt for a deadline upon activation.

Apologies for any issues this has caused, the team has this on their radar to come up with a solution that offers the best of both worlds - an option to Prompt, AND an option to set a duration in order to allow automations such as our Workflows feature to handle campaigns seamlessly.

1 Like
6

Thanks Stephen. I wholeheartedly support that flexibility with campaign deadlines. Any idea on what the timeline would be to rollback for now till a solution is identified?

some context on my use case Creating a certification due to a transfer scenario but excluding some apps that may not need to be certified. I am using a workflow for this but using the http action to call create campaign instead of the native create campaign action due to not being able to set a exclusion campaign filter within the Create Campaign action itself. It would be great if the Create Campaign action was mirrored to the beta/campaign API call in my opinion.

1 Like
7

that is the EXACT scenario we were trying to solve for :slight_smile:

I believe they are trying to expand the built-in Create Campaign card to have more functionality, but at times, the raw hTTPRequest call to beta/campaigns allows tighter customization.

I havent seen specifics (Im a solution architect here, not a developer) on timelines, but I believe the rollback might be this week (if done at all), and most likely a proper solution within 2-3 months pending any interruptions or higher priority work.

1 Like