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

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.

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?

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.

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

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

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

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

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")

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.