Can't edit query results in ARO

Dean_Mrazek

Hi

I'm trying to edit a query in a user creation/user re-activation ARO to add in a new group that we can select to re-activate accounts from. However, whenever I try to edit the query all the options are greyed out. I also tried selecting Active Directory User and re-creating the query from scratch in the prompt but then when I try to save the ARO it tells me the query needs to be mapped. However, checking the same ARO in a different environment, that query is not mapped to anything.

Screen shot below of greyed out configure query screen.

Geoff_Ross

Hi Dean,

There's a lot of complexity here but you can avoid mapping it if you consume it into another prompt by including it in the criteria. It could have been that, or it could have been removed from mapping after the fact because its only a UI validation.
The safest way is to just map everything like you have into one big block (but with spices) and then everything will keep working fine even if you change criterial, remove prompts etc.

Geoff

Simon_Zeinhofer

When you recreate the query from scratch, don't forget to select, under which relationship these items shall be added to your work item. You find it in the last section "Options". If you don't select neither "Related Items" nor "Affected Items", an error occurs when you try to save the ARO.

Dean_Mrazek

Hi

I double checked that the related items option was ticked and it looks like screenshot below

However, I still get this error message

Simon_Zeinhofer

@Dean_Mrazek This means that the prompt "Begin typing to search for a deactivated User" is not mapped to anything. I guess this is a string field? So you have to map it to the Work Item that lies below this RO.

The "Query Results prompts for which a relationship was not configured" is always present, but in your case no query Results are stated below that, so you can ignore that. If a relationship is not configured for one or more query result prompts, it would be stated below.

Dean_Mrazek

Hi @Simon_Zeinhofer

While looking at the ARO prompts I found this

And checking the xml for the management pack for this ARO I found this:

<Source Id="eb8ab2a5-da7d-40b6-bfff-19d9ebfcd337" Ordinal="4" Prompt="User to reactivate"

It looks to me I need to replace the second Prompt in that ([Prompt_eb8ab2a5-da7d-40b6-bfff-19d9ebfcd337_Default]) with adding in the prompt that keeps returning the message in the previous post so it looks like this?

Simon_Zeinhofer

We see this behavior, when more than one prompt is mapped to the same property in the Work Item too. Normally it doesn't matter and the mapping still works.

@Geoff_Ross : Is this an issue with the ARO Builder? I mean that these prompts are shown with their guid and not the name when placed directly near each other?

Geoff_Ross

Hey Community

Simon, There is a open bug for when mapping tokens messing up when mapped directly next to each other without a space.
We are working on this but ARO bugs have a different development cycle and very rigorous QA process to avoid multiple releases - due to the Last Modified date thing).

Dean, I suggest you recreate the prompt, get the criteria right and then remap all the prompts to whatever property that is with a space between each one.

Geoff

Dean_Mrazek

Hi

Thanks! I had a go at that, however, I'm not sure the prompt that needs to be mapped was ever mapped in the original ARO. Looking through the XML of the advanced request offering management pack I can't find the prompt ID anywhere I would expect it to be with regards to mapping or multiple mapping. Could it possibly be mapped somewhere else and I just can't see it?

Geoff_Ross

Hi Dean,

There's a lot of complexity here but you can avoid mapping it if you consume it into another prompt by including it in the criteria. It could have been that, or it could have been removed from mapping after the fact because its only a UI validation.
The safest way is to just map everything like you have into one big block (but with spices) and then everything will keep working fine even if you change criterial, remove prompts etc.

Geoff

Dean_Mrazek

Hi Geoff, turns out it was user error. I had thought that the criteria that used the prompt that was not mapped (Begin typing to search for a deactivated user: String) was manually typed in. I didn't realise that I had to click on "Set Token" to properly get the third prompt consumed by another. Thanks so much @Geoff_Ross and @Simon_Zeinhofer!