Checkpoint file output connection based on metadata

Post Reply
loicaigon
Advanced member
Posts: 379
Joined: Wed Jul 10, 2013 10:22 am

Checkpoint file output connection based on metadata

Post by loicaigon »

Hi All,



I have a checkpoint for an operator to validate a file. Actually he has to choose into which connection the file has to be outputted.



I wish i could not expose the connections list and have the connection determined by the usr choice.



Here is a screenshot of what I have in mind :







The reason why I want that is that I want the operator to fill a message if he refuses the job.

Actually he has to do two operations, say YES and pick the OK folder



Plus, he may say NO and unspite of all select the OK folder. So for consistency, I would like to deal with file output. I just want the user to say if he validates or not the file.



Is that feasible ?



Thanks in advance for your inputs,



Best regards,



Loic
dkelly
TOP CONTRIBUTOR
Posts: 658
Joined: Mon Nov 29, 2010 8:45 pm
Location: Alpharetta GA USA
Contact:

Checkpoint file output connection based on metadata

Post by dkelly »

Can you make the connection names the "imprime" choices?
loicaigon
Advanced member
Posts: 379
Joined: Wed Jul 10, 2013 10:22 am

Checkpoint file output connection based on metadata

Post by loicaigon »

Hi Dwight,



Thanks for your interest. Sure I could but what matters me is that if the operator wants to discard the file, I want to force him to justify why. If I only work with connections, I may not know why he refused some file.



And If I lt the field no matter what, the user won't understand why he may have to fill some "unapproval reason'" while h is actually ok with the file.



So what I would like is him to say Yes or No. If YES=>OK, if No=> WHY anf then I deal with connections backstage depending on the YES/NO metadata value.



Thanks anyway,



Loic
dkelly
TOP CONTRIBUTOR
Posts: 658
Joined: Mon Nov 29, 2010 8:45 pm
Location: Alpharetta GA USA
Contact:

Checkpoint file output connection based on metadata

Post by dkelly »

What you want to do is not currently supported by Switch. I'd recommend that you file a feature request
loicaigon
Advanced member
Posts: 379
Joined: Wed Jul 10, 2013 10:22 am

Checkpoint file output connection based on metadata

Post by loicaigon »

Thanks a lot Dwight,



I will ;)
dkelly
TOP CONTRIBUTOR
Posts: 658
Joined: Mon Nov 29, 2010 8:45 pm
Location: Alpharetta GA USA
Contact:

Checkpoint file output connection based on metadata

Post by dkelly »

Try this



Properties





Switch Client approve = "Yes"





Switch Client approve = "No"

loicaigon
Advanced member
Posts: 379
Joined: Wed Jul 10, 2013 10:22 am

Checkpoint file output connection based on metadata

Post by loicaigon »

Hi Dwight,



Thanks again for your effort. What you offer is logical and indeed what I do. Problem is, there is still place for manual errors. I mean that user can "reject", states why and though might pick the ok folder. So the file will be possibly printed inspite of the operator decision.



And another end, user can validate the file and pick the "fail" folder. So one file would be discarded with no reasons.



I was hoping to have a better management of the file routing here.



Thanks a lot anyway :)
dkelly
TOP CONTRIBUTOR
Posts: 658
Joined: Mon Nov 29, 2010 8:45 pm
Location: Alpharetta GA USA
Contact:

Checkpoint file output connection based on metadata

Post by dkelly »

right, but that's why you only have 1 outgoing connection and have Switch sort jobs using the metadata value from SwitchClient to route the job automatically.
loicaigon
Advanced member
Posts: 379
Joined: Wed Jul 10, 2013 10:22 am

Checkpoint file output connection based on metadata

Post by loicaigon »

Hi Dwight,



Yeah you are right, that's the way to go. Thanks a lot. Still worth a feature request though :)
Post Reply