Hi all. I have a web service connector, on which there is not working account status.
On application, I have an attribute called STATUS (in uppercase), with values Ativo and Inativo.
As in other implementations I configured status behaviour like this:
However, accounts with STATUS field with “Inativo” value appears as Enabled (in fact, all accounts from that source appears as Enabled):
Am I missing something?
Did you add Account Status Enable Attribute config after your first aggregation ?
I have faced this sometimes,
Try Aggregation without optimization
Reset source accounts and aggregate again
Hi Krishna! Yes, I configured status after first aggregation. I cleared accounts and performed aggregation without optimization, but all accounts still remain enabled.
Tried also:
modify attribute name to STATUSBIS (for confirming if there was something with name), to status (lowercase) and re creating a whole new source, but in all cases status=Inativo does not brings account to disabled status.
Hi Julian, just check that the field ‘IIQDisabled’ is in your code rule.
For example:
Map mapa = new HashMap();
String IIQDisabled = “true”;
if(STATUS.equals(“Active”)){
IIQDisabled = “false”;
}
mapa.put(“IIQDisabled”, IIQDisabled );
Also try to add the attribute IIQDisabled and the value in the ‘Account Enable Status Attribute’ option
We could make it work, but I do not feel confortable with solucion.
What we made is to add a new attribute named IIQDisabled, we force it to come with true value for that “Inativo” value. Then we configured the enabled account:
I have created a bunch of web services, this IIQ Disabled is required in JDBC, but for Web Services, you dont need, this should work with Account Enable Status Attribute.
Yes, very weird, I have also other web services connectors working fine with the account enable status.
Hi! Faced same issue in other client.
It appears that when modifying response in the after operations rule, the status mapping loses.
Solution is to add the iiqdisabled attribute to the mapping:
Map updatedMapInfo = new HashMap(); // modified web service respone
List finallist = new ArrayList(); // array of new accounts
....
Map newmap = HashMap(); // final account
...........
String IIQDisabled = "true";
if(JsonUtil.get(jsonNode, "status").equals("Active")) // transforms an status with value Active to the iiqDisabled = false
IIQDisabled = "false";
finallist.add(newmap);
.....
updatedMapInfo.put("data", finallist);
return updatedMapInfo; // return new array of accounts to source
also, I have to put iiqDisabled attribute on source schema:
add it to the account aggregation operation mapping:
and finally, add it to the connection settings screen:
hi @jsosa, does this behaviour happen when the after operation rule is attached to account aggregation operations only or to other operations as well.
When the Account is disabled using Disable Account Operation does the account show as disabled immediately for you or do you have to run a single or full account aggregation to see the status updated as Disabled
Hi Uday, only in account aggregation, and apparently only when I modify the original response. I have a rule that prints all request/response information to log that I use in almost all operations, and it does no affects the account status.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
