+44(0)1908 545 770
YOUR EXPERT RPA PARTNER

Team up with our RPA strategy and tech specialists for maximum automation impact

Find out more
Harness the power of UiPath in your business.
WATCH NOW

Save money and spend more time on priority work.

Book consultation
READY, SET, AUTOMATE

Let's choose, design and deploy a process automation solution for your business.

Find out more
TRANSFORM YOUR BUSINESS

Let's analyse your business to discover opportunities for innovation and automation.

Find out more

Begin your business transformation journey

Book consultation
AUTOMATE EVERY FUNCTION

Automate where it matters most. Scale to solve challenges in every area

Find out more
GIVE EVERY TEAM THE TOOLS FOR SUCCESS

Equip people with user-friendly solutions that save time and make work easier

Find out more

Which business problem
can we solve first?

Book consultation
10 October 2014

How to fix the K2 Appit task notification that only displays System.string[] in the email

This post explains how to fix an issue that causes only the text System.string[] being displayed in a new K2 Appit task notification email.

It happens when any part of the notification contains a SharePoint property that is of type User.  The obvious fix is to map this SharePoint field’s value to a K2 data field and use that in the email.

K2 Automated Testing Software

BenchQA allows full test automation of K2, including fully automated K2 SmartForms and K2 Workflow testing. It promotes test driven development for K2 and ensures continued quality assurance for K2 solutions. Easily apply changes to test cases to accommodate changes to K2 apps and ensure all apps are regression tested to avoid defects and assure continuous quality.

 

Free K2 Five Upgrade Review

K2 Appit - List column's of type Person value casing System.string[] issue

K2 Appit – List column’s of type Person value casing System.string[] issue


K2 Appit - Work item notification only display System.string[] in email

K2 Appit – Work item notification only display System.string[] in email

Again, tt happens when any part of the notification contains a SharePoint property that is of type User.  The obvious fix is to map this SharePoint field’s value to a K2 data field and use that in the email.

K2 Appit - Use data field in notification to avoid System.string[] issue

K2 Appit – Use data field in notification to avoid System.string[] issue

The issue with this approach is that K2 seems to map the user’s fully qualified name (FQN)  into the data field, not the user’s actual display name.

K2 Appit - User Name value renders K2 FQN

K2 Appit – User Name value renders K2 FQN

The “Employee (Value)” field is the SharePoint value of the user.  The System.sting[] issue is now fixed, but the user’s display name is still not displayed.

How to get a user’s display name in K2 Appit from the FQN?

Open the K2 Appit SmartObject and add a new field “Employee (Display Name)” of type text.

K2 Appit - Add New Employee Properties

K2 Appit – Add New Employee Properties

Open the SmartObject method that does the user details lookup and map the input and output fields.

K2 Appit - Map Add New Employee Properties to SmartObject mehod

K2 Appit – Map Add New Employee Properties to SmartObject mehod

Using the K2 Appit SmartObject tester, execute the method and see the correct details being returned.  This include the user’s display name.

K2 Appit - Execute list smartobject with new employee properties and view results

K2 Appit – Execute list smartobject with new employee properties and view results

The new property can now be used in the K2 Appit process and the user’s display name will correctly be looked up.

K2 Appit - User Name value renders K2 FQN - Email setupc

K2 Appit – User Name value renders K2 FQN – Email setupc

This post highlights how flexible the K2 Appit platform is.  There are many utilitarian and helper SmartObjects, properties and methods available that can be explored using the K2 Appit SmartObject explorer.  The results of which can help you find solutions like the ones above.

Need further technical advice or support?