Identity Broker Forum

Welcome to the community forum for Identity Broker.

Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.

0
Answered

Workday Identity Broker information

Werner Deysel 7 years ago in UNIFYBroker/Workday updated by anonymous 7 years ago 3

Hi,


I would like to know somethings about the Workday Identity Broker.


1. Does the Identity Broker honor the Workday +7 hrs time difference or does it ignore it?

2. What data gets imported via the Delta stages when it Imports it from Workday?


Would anyone be able to assist in finding out those questions


Kind Regards

Werner

Answer
anonymous 7 years ago

Hi Werner,

1. Are you referring to the buggy/inconsistent handling of time-zones by Workday? If so, the connector accounts for it where we have noticed it being an issue. Currently this is on the Polling import calls (Worker and Organization - using the timezone offset setting), as well as the comparison against hire date and seniority date (uses a date comparison instead of time based).

2. I've added a note to the Usage section on the Workday Worker Connector.

Thanks.

0
Declined

Account Expired due to Excessive Failed Sign On

Werner Deysel 7 years ago in UNIFYBroker/Workday updated by anonymous 7 years ago 5

Hi,


I recentley change my Password for the Workday Agent Account, and it keeps locking the Workday Account as excessive logins.

Is this something that was change recentley to Workday, i still rememer only changing it in 1 place and then it would not lock the account again, not sure if this might have changed, even left it for 24hr to propegate and it still locks the account.


I also notice that the Active Connections goes to about 12 then back to 2.


Here are the versions that i am Running.

Workday Connector

Identity Broker

5.0.0.5

V 5.0.4



Answer
anonymous 7 years ago

Nothing has changed in the connector code. I'd recommend contacting our support as it sounds like Workday have broken something again - and at the very least would require some analysis of what's going on.

Thanks.

0
Answered

The Connector Does not support anchor modification

Werner Deysel 7 years ago in UNIFYBroker/Workday updated by anonymous 7 years ago 1 1 duplicate

Hi,

i dont find much documentation on error codes for the Identity Broker, but this anchor modification is a new error that i see in the exporting errors.

Can someone explain to me what this is, and how to fix this?

Answer
anonymous 7 years ago

Hi Werner,

This is currently documented at Anchor Modification and Handling Renames. It means that the solution is attempting to update the value of the key field for the connector - for a connector that doesn't support the operation. The fix is to stop attempting these operations.

Thanks.

0
Completed

NEWS-LTD-101: Idb for Workday: Request to change filtering date from hire date to current date

Jeff Nelson 7 years ago in UNIFYBroker/Workday updated by anonymous 7 years ago 1

News has requested that UNIFY modify the code for IdB for Workday such that filtering on a user;s Top-Level Org uses the current date rather that the target user's Hire Date. Currently News are seeing users filtered that should not be filtered and the cause appears to be that when the hire date is used, the IdB returns the SupervisoryOrg level instead of the Top Org level for the user i.e. the returned result is:
 SupervisioryLevelOrganisation = SupervisioryOrg
 TopLevelOrganisation = SupervisioryOrg
Which results in the user being filtered

News-Ltd now have given approval for UNIFY to make to the requested code change and agree that (in the absence of advice from Theory of Mind), that they take full responsibility for the performance of the code and have agreed that the code change will be staged through a full regression test cycle in their UAT environment prior to migrating the code to Production.

Thanks Jeff.

0
Answered

Value cannot be null. Parameter name: id at Unify.Product.IdentityBroker.FilteredWorkerIdsCache.Contains(String id)

Carol Wapshere 8 years ago in UNIFYBroker/Workday updated by anonymous 8 years ago 4

News have opened a support call - it looks like the Identity Broker Workday Employees connector is not importing any data, and may not have been importing for at least a couple of days. This is the error in the log where it says the import failed. The customer has also sent me the full log file.

20161019,22:20:24,UNIFY Identity Broker,Connector,Warning,"Import all entities from connector failed.Import all entities from connector Workday Employee failed with reason Value cannot be null.
Parameter name: id. Duration: 01:33:15.1564315
Error details:
System.ArgumentNullException: Value cannot be null.
Parameter name: id
at Unify.Product.IdentityBroker.FilteredWorkerIdsCache.Contains(String id)
at Unify.Product.IdentityBroker.WorkdayWorkerConnector.FilterWorker(IWorkdayCommunicator communicator, FilteredWorkerIdsCache filteredWorkerIdsCache, HashSet`1 organisationFilters, String workerID, WorkdayWorker currentWorker, Action`1 rejectItemAction, ICollection`1 cacheFiltered, ICollection`1 emailFiltered, ICollection`1 hireDateMissingFiltered, ICollection`1 orgFiltered, ICollection`1 permanentFiltered)
at Unify.Product.IdentityBroker.WorkdayWorkerConnector.<GetWorkers>d__16.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__10`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ProduceAutoPages>d__7`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at Unify.Framework.Visitor.VisitEvaluateOnThreadPool[T](IEnumerable`1 visitCollection, Action`2 visitor, Int32 maxThreads)
at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities)
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass27_0.<Run>b__0()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
20161019,22:20:24,UNIFY Identity Broker,Change detection engine,Error,"Change detection engine import all items failed.
Change detection engine import all items for connector Workday Employee failed with reason Value cannot be null.
Parameter name: id. Duration: 01:33:15.1714330
Error details:
System.ArgumentNullException: Value cannot be null.
Parameter name: id
at Unify.Product.IdentityBroker.FilteredWorkerIdsCache.Contains(String id)
at Unify.Product.IdentityBroker.WorkdayWorkerConnector.FilterWorker(IWorkdayCommunicator communicator, FilteredWorkerIdsCache filteredWorkerIdsCache, HashSet`1 organisationFilters, String workerID, WorkdayWorker currentWorker, Action`1 rejectItemAction, ICollection`1 cacheFiltered, ICollection`1 emailFiltered, ICollection`1 hireDateMissingFiltered, ICollection`1 orgFiltered, ICollection`1 permanentFiltered)
at Unify.Product.IdentityBroker.WorkdayWorkerConnector.<GetWorkers>d__16.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__10`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ProduceAutoPages>d__7`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at Unify.Framework.Visitor.VisitEvaluateOnThreadPool[T](IEnumerable`1 visitCollection, Action`2 visitor, Int32 maxThreads)
at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities)
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass27_0.<Run>b__0()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
Answer
anonymous 8 years ago

From analysis between the latest version and the version that presented the problem, it can be seen that there is a difference in the logic for filtered workers. An improvement had already been made to ensure that rescinded workers do not cause the filter logic to fail (as they tend to get imported partially populated).

0
Completed

Test Use case for 'adding' new phones only to Workday

Jacques Swanepoel 8 years ago in UNIFYBroker/Workday updated by anonymous 8 years ago 1

We need to test this use case given the changes to how we use the contact object

Answer
anonymous 8 years ago

Contact update split up to ensure that changes are 'nursed' into Workday.

0
Completed

Public Field for Telephone Number structure

Jacques Swanepoel 8 years ago in UNIFYBroker/Workday updated by anonymous 8 years ago 1

Add Public field to the telephone number structure to ensure that the public/private status of a number is honoured

Answer
anonymous 8 years ago

Done. Thanks.

0
Completed

Allow timezone configuration for watermark in the WD Connector for IDB

Jacques Swanepoel 8 years ago in UNIFYBroker/Workday updated by anonymous 8 years ago 2

Workday have confirmed that they cannot change their timezone in Workday to match the UTC timezone we use in our Import Changes requests. Given our client is located across 12 different timezones, this means that we miss a lot of the (utc-x) requests. Would it be possible to add a timezone offset to the Connector so that we can change this to match the Workday set timezones? This will allow for a consistent set of changes to be detected

Answer
anonymous 8 years ago

Workaround added to the connector, the attribute is timezoneOffset using xml encoded timespan (see duration examples here for details on the value, e.g. -PT13H for offsetting 13 hours prior to UTC now).

0
Completed

Update to the IDB connector for WorkDay adding flatterned addresses and phone numbers

Jacques Swanepoel 9 years ago in UNIFYBroker/Workday updated by anonymous 9 years ago 6

Please look at adding the following fields to the WorkDay Connector:

  • Primary Business Address (Formatted_Address based of the primary="true" type="WORK"
  • Priimary Business Office Phone (Formatted_Phone based of the primary="true" type="WORK" usage descriptor="Telephone")
  • Primary Business Mobile Phone (Formatted_Phone based of the primary="true" type="WORK" usage descriptor="Mobile")
  • Primary Private Mobile Phone (Formatted_Phone based of the primary="true" type="HOME" usage descriptor="Mobile")
0
Completed

Feature request - ability to update non-primary work address

Adam van Vliet 10 years ago in UNIFYBroker/Workday updated by anonymous 9 years ago 1

Add the ability to update non-primary work address. The type of address should be configurable if possible, otherwise hard-code to work address. It should be the non-primary address.

The rules in Workday will ensure that there is only one address that satisfies these conditions.