xCP 2.1 Long Users Names Issue

Dear experts,

For one of our clients (using xCP 2.1 Patch 16) we have recently discovered a major issue: a few users names inside the repository are longer than 32 characters causing the tasks that have as performer Individual users and group members at the same time to fail, since xCP is not able to compute the performer name. It seems that somewhere the users names longer than 32 characters are truncated.

The application is already deployed to PROD and ready to go live, but this issue stops us.

Has anyone encounter this issue before? Is there any workaround for this situation?

Kind Regards,

George

Find more posts tagged with

Comments

ashrafsyed

If you have the complete stack trace, can you attach it here ?

Can you also give me the steps to reproduce this issue inhouse ?

george.grama@ro-planet.ro

I couldn't find any errors in the logs.

To reproduce it, you can create a simple process using xCP Designer, with two manual activities: first one with workflow supervisor as performer and for the second one we have used Group from Parameter, Processed by Individual users and group members at the same time.

We have a parameter storing the group name.

Create a few users with user_name longer than 32 characters and assign them to the group then launch the workflow.

All the tasks that should've been assigned to those users will be assigned to the workflow supervisor.

ashrafsyed

can you pass me the output of this DQL command ?

describe dmi_workitem

george.grama@ro-planet.ro

Here's the result:

actual_start_date Time/Date Started

a_content_type Char(32) Format

a_operations Char(16) Operation

content_type Char(32) Format

date_sent Time/Date Sent

delete_flag Boolean Dequeued

dependency_type Char(10) Dependency Type

dequeued_by Char(255) Dequeued By

dequeued_date Time/Date Dequeued Date

due_date Time/Date Due Date

event Char(64) Event

event_detail Char(2000) Event Detail

instruction_page Integer Instruction Page

item_id ID Object ID

item_name Char(255) Name

item_type Char(32) Type

i_event_flags Integer Event Flags

i_is_replica Boolean Is Replica

i_partition Integer i_partition

i_vstamp Integer Version Stamp

message Char(800) Message

name Char(255) Recipient

next_tasks_type Char(10) Next Task

plan_start_date Time/Date Start Date

position Double Position

priority Integer Priority

read_flag Boolean Read

remote_pending Boolean Distribute to Other Docbases

router_id ID Router ID

sent_by Char(255) Sender

sign_off_date Time/Date Signed Off

sign_off_required Boolean Sign Off Required

sign_off_user Char(255) Sign Off User

source_docbase Char(120) Source Docbase

source_event ID Source Event

source_stamp Integer Source Stamp

stamp ID Stamp ID

supervisor_name Char(255) Supervisor

target_docbase Char(120) Target Docbase

task_name Char(128) Task Name

task_number Char(5) Task Number

task_state Char(10) Status

task_subject Char(512) Task Subject

task_type Char(10) Task Type

IslamMujahid

We encountered this issue but for "Get Next Task" action and were able to resolve it by modifying dbo.dm_get_next_task procedure directly in underlying database.Increase the length of @username attribute. Hope this helps.

ashrafsyed

You seems to send me the definition of dmi_queue_item not dmi_workite.

In either case, pleas involve support to raise consult request as this require through investigation.