Form Guide Conversions

[Former Community Member]

I created a basic process using a form guide to display a form and then submit it to another user. When I initiate the process in Workspace, it indicates that The requested form produced errors. Contact the system administrator or see the server error log for details. When I look at the server log, I see an ALC-FRM-001-022 error, but looking at the Error Code Reference manual doesnt tell me much.



I'd be happy to include a partial server log, if it would help. The full server log is just too large.



TIA

[Former Community Member]

Updates.<br /><br />At different times, I tried different things and got the following errors: ALC-WKS-007-027 and ALC-FRM-001-501. When I saw the last one, I realized that my submit button in the xdp form was emailing the xdp form. I changed the submit button to submit XML, but I still get the same error within Workspace, "The requested form produced errors. . . ." The error code is the same as above. I am including that portion of the log:<br />. . .<br />2007-12-18 14:50:58,296 ERROR [com.adobe.formServer.FormsServlet] ALC-FRM-001-022: Unexpected exception: com.adobe.forms.guide.GuideGenerator: Missing <guides> tag<br />2007-12-18 14:50:58,828 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl retrieveEvent<br />INFO: retrieving active event for 112<br />2007-12-18 14:50:58,843 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl retrieveEvent<br />INFO: retrieved active event for 112<br />2007-12-18 14:50:58,859 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl sendNotifications<br />INFO: Total subscriptions retrieved = 2 for event id112<br />2007-12-18 14:50:58,890 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl createNotifications<br />INFO: Now creating notifications.<br />2007-12-18 14:50:58,906 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl createNotifications<br />INFO: Created 2 notifications.<br />2007-12-18 14:50:58,906 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl retrieveEvent<br />INFO: retrieving active event for 112<br />2007-12-18 14:50:58,921 INFO [STDOUT] Dec 18, 2007 2:50:58 PM com.adobe.idp.event.notification.NotificationManagerImpl retrieveEvent<br />INFO: retrieved active event for 112<br />2007-12-18 14:50:59,031 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Now delivering notification to service RemoteEvents<br />2007-12-18 14:50:59,031 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Now delivering notification to service operation onEvent<br />2007-12-18 14:50:59,031 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Now delivering notification to service operation parameters {eventType=TaskCreated}<br />2007-12-18 14:50:59,046 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Notifications delivered<br />2007-12-18 14:50:59,046 INFO [com.adobe.livecycle.remoteevents.client.RemoteEventClient] message received type: event<br />2007-12-18 14:50:59,046 INFO [com.adobe.livecycle.remoteevents.client.RemoteEventClient] message received part 1: {data=[B@2cc99f, event=TaskCreated}<br />2007-12-18 14:50:59,046 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl disableNotification<br />INFO: Attempting to disable the notification after delivery.<br />2007-12-18 14:50:59,046 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Now delivering notification to service OrchestrationEventHandler<br />2007-12-18 14:50:59,046 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Now delivering notification to service operation onEvent<br />2007-12-18 14:50:59,046 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Now delivering notification to service operation parameters {eventTemplateId=STRT_ER1172599333679, serviceName=Task Assignment, eventTemplateType=eventReceiveAsStartTemplate, eventTypeName=TaskCreated}<br />2007-12-18 14:50:59,062 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl disableNotification<br />INFO: Attempting to disable the notification after delivery.<br />2007-12-18 14:50:59,078 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.workflow.dsc.service.OrchestrationEventListenerService onAsynchronousEvent<br />INFO: ProcessManagerSerice:onAsynchronousEvent()<br />2007-12-18 14:50:59,078 INFO [com.adobe.workflow.AWS] Invoking action synchronously<br />2007-12-18 14:50:59,078 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.util.EventDBHelper getActiveEventByPrimaryKey<br />INFO: Event with id 112 is already disabled, EventService will not deliver notification.<br />2007-12-18 14:50:59,078 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.livecycle.notification.TaskNotificationServiceImpl taskAssignment<br />INFO: TaskNotificationService called taskAssignment: 111<br />2007-12-18 14:50:59,078 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.livecycle.notification.TaskNotificationServiceImpl handleNotificationEvent<br />INFO: TaskNotificationService called handleAssignmentOrReminderEvent: 111<br />2007-12-18 14:50:59,078 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl updateEventStatus<br />INFO: Event with id 112 is already inactive.Event instance with id 112 is inactive for TaskCreated<br />2007-12-18 14:50:59,109 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl deliverNotificationToService<br />INFO: Notifications delivered<br />2007-12-18 14:50:59,109 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl disableNotification<br />INFO: Attempting to disable the notification after delivery.<br />2007-12-18 14:50:59,125 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl disableNotification<br />INFO: Attempting to disable the notification after delivery.<br />2007-12-18 14:50:59,140 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.util.EventDBHelper getActiveEventByPrimaryKey<br />INFO: Event with id 112 is already disabled, EventService will not deliver notification.<br />2007-12-18 14:50:59,156 INFO [STDOUT] Dec 18, 2007 2:50:59 PM com.adobe.idp.event.notification.NotificationManagerImpl updateEventStatus<br />INFO: Event with id 112 is already inactive.Event instance with id 112 is inactive for TaskCreated<br /><br />HTH, thank you!

[Jasmin_Charbonn]

Before rendering a form into a guide, you need to "guide enable" that form.<br /><br />That means you need to use guide builder to create the guide that's going to be display for your form. That adds some tags in the XDP. Did you do that?<br /><br />I'm concerned with that message : GuideGenerator: Missing <guides> tag <br /><br />Jasmin

[Former Community Member]

No, I didn't add any tags. I figured that Workspace would grab a pdf or xdp form and display it. This is not intuitive. Could you point me to a document or tutorial where I could see what tags I need to insert and where?



Thanks!

[Jasmin_Charbonn]

You don't add the tags manually. You need to use the Guide Builder within Adobe Form Designer to create the guide associated with form. It'll take care of adding the tags when you save the guide.



Jasmin

[Former Community Member]

I appreciate your quick response, but after looking more into Guide Builder, this is not the way that I want to go with this process. At this point, I need something simpler, like . . . display a form in WS, enter data, submit to another WS user to view, approve, reject, and/or send back to the process creator for additions/corrections. At this point, the process creator may submit or abandon.



In a previous incarnation of the process, I was emailing a pdf of the completed form to a user to perform the above actions. I need to make the form available within WS. Do I submit as an XML? What kind of submit do I include in the xdp form to display within WS?



Thanks!

[Former Community Member]

If I'm allowed to continue http://www.adobeforums.com/webx?128@@.3bc4ac76 here, I tried changing my form to xml submission instead of pdf, so I can display it in WS. When doing this, I got the error described in the above thread (ALC-WKS-007-043).



I'm using an xfaForm variable, as suggested in the above thread, and Render/Submit PDF Service from Samples - Forms, as suggested elsewhere. The above thread was interrupted when you asked for the the last error in the server log. Here's what I get:



2007-12-19 10:25:00,046 INFO [STDOUT] [Flex] [ERROR] Error handling message: flex.messaging.MessageException: com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@b39023 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)

operation = submitWithPriorData

clientId = 747C6160-11C1-3463-A4E8-C054E1498068

destination = task-actions

messageId = AC72A636-529D-79AA-24EC-F301177967F1

timestamp = 1198077899921

timeToLive = 1198077899921

body = null

hdr(DSEndpoint) = workspace-polling-amf

hdr(DSId) = 6EF70AF3-E198-379C-2448-5D25958D60BA

errorReply: Flex Message (flex.messaging.messages.ErrorMessage)

clientId = 747C6160-11C1-3463-A4E8-C054E1498068

correlationId = AC72A636-529D-79AA-24EC-F301177967F1

destination = task-actions

messageId = 747C7472-E0D8-5634-A5AE-C0DE12A18980

timestamp = 1198077900046

timeToLive = 0

body = null

code = Server.Processing

message = com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@b39023 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

details = null

rootCause = ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@b39023 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

body = null

extendedData = null

2007-12-19 10:25:00,046 INFO [STDOUT] [Flex] Error handling message: flex.messaging.MessageException: com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@b39023 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)

operation = submitWithPriorData

clientId = 747C6160-11C1-3463-A4E8-C054E1498068

destination = task-actions

messageId = AC72A636-529D-79AA-24EC-F301177967F1

timestamp = 1198077899921

timeToLive = 1198077899921

body = null

hdr(DSEndpoint) = workspace-polling-amf

hdr(DSId) = 6EF70AF3-E198-379C-2448-5D25958D60BA

errorReply: Flex Message (flex.messaging.messages.ErrorMessage)

clientId = 747C6160-11C1-3463-A4E8-C054E1498068

correlationId = AC72A636-529D-79AA-24EC-F301177967F1

destination = task-actions

messageId = 747C7472-E0D8-5634-A5AE-C0DE12A18980

timestamp = 1198077900046

timeToLive = 0

body = null

code = Server.Processing

message = com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@b39023 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

details = null

rootCause = ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@b39023 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

body = null

extendedData = null



Hope you can continue to help me within this thread.



Thank you!

[Jasmin_Charbonn]

I don't see how using guide builder make your process more complicated. In fact it has nothing to do with it.



When you build your process in workbench, your going to design the logic flow. In you case "display a form in WS, enter data, submit to another WS user to view, approve, reject, and/or send back to the process creator for additions/corrections".



In your case you'll probably have a few User steps and some intermediate data processing step. You'll have to define a form variable, probably of type xfaForm that will point to an XDP.



Now when you create that variable you can associate a render service that will render the form back in WorkSpace. At that point you can decide to render a Form Guide, a PDF, HTML. It's your choice. The process logic is not changed. It's really just the Render service that you choose that defines how the form is going to show.



The only thing is if you choose to render a guide, you need to start the guide builder, which will create you a default guide, then save and close it so you have the guide section in your XDP.



Let me know if this is not clear.



Jasmin

[Former Community Member]

Thank you for your answer. I understand what you are saying, but I can't spend the time, right now, trying to understand and learn the Guide Builder. This is the reason why I feel the process would get more complicated. Using the Guide Builder can definitely make the form look nicer, but this is not necessary at this stage. This is why I decided to go the other way.



I've received an answer under
"Error ALC-WKS-007-043" from WorkflowUser. Would you have anything else to add to that? I thought that I'd need two different variables, one for receiving the form data (input) and one to output the data, but WorkflowUser said to use the same one for input and output. I am in the process of setting up the email server.



Thank you!

[Jasmin_Charbonn]

Yes. Use the same variable for Input and Output.



Are you using the "Render PDF Form" service from the Sample - Forms category?



Jasmin

[Former Community Member]

OK, I'll use the same variable.



Yes, I'm using that render service and the submit service from the same category.



Thanks!

[Jasmin_Charbonn]

Don't use any submit service. It should submit fine wihtout any.



Jasmin

[Former Community Member]

I removed the submit service and got the following error: "An error occurred submitting the form (task 123, form 0). (ALC-WKS-007-043)"



I believe that removing the submit service caused the error. See below for the portion of the log related to the latest error:



2007-12-20 13:27:42,140 INFO [STDOUT] [Flex] [ERROR] Error handling message: flex.messaging.MessageException: ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.

incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)

operation = submitWithPriorData

clientId = 1572CAEC-1008-07E2-FB6D-22EA20067A89

destination = task-actions

messageId = 14436202-BB8D-687C-5866-F8CEAED4B0C7

timestamp = 1198175261968

timeToLive = 1198175261968

body = null

hdr(DSEndpoint) = workspace-polling-amf

hdr(DSId) = 156F1081-021B-B384-EB01-7EA7D18A6A24

errorReply: Flex Message (flex.messaging.messages.ErrorMessage)

clientId = 1572CAEC-1008-07E2-FB6D-22EA20067A89

correlationId = 14436202-BB8D-687C-5866-F8CEAED4B0C7

destination = task-actions

messageId = 1572CC8F-FC0D-D9E4-3FA8-111E0B053C31

timestamp = 1198175262140

timeToLive = 0

body = null

code = Server.Processing

message = ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.

details = null

rootCause = org.xml.sax.SAXParseException: Content is not allowed in prolog.

body = null

extendedData = {message=ALC-WKS-005-029, cause=com.adobe.idp.taskmanager.dsc.client.task.TaskManagerException}

2007-12-20 13:27:42,140 INFO [STDOUT] [Flex] Error handling message: flex.messaging.MessageException: ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.

incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)

operation = submitWithPriorData

clientId = 1572CAEC-1008-07E2-FB6D-22EA20067A89

destination = task-actions

messageId = 14436202-BB8D-687C-5866-F8CEAED4B0C7

timestamp = 1198175261968

timeToLive = 1198175261968

body = null

hdr(DSEndpoint) = workspace-polling-amf

hdr(DSId) = 156F1081-021B-B384-EB01-7EA7D18A6A24

errorReply: Flex Message (flex.messaging.messages.ErrorMessage)

clientId = 1572CAEC-1008-07E2-FB6D-22EA20067A89

correlationId = 14436202-BB8D-687C-5866-F8CEAED4B0C7

destination = task-actions

messageId = 1572CC8F-FC0D-D9E4-3FA8-111E0B053C31

timestamp = 1198175262140

timeToLive = 0

body = null

code = Server.Processing

message = ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.

details = null

rootCause = org.xml.sax.SAXParseException: Content is not allowed in prolog.

body = null

extendedData = {message=ALC-WKS-005-029, cause=com.adobe.idp.taskmanager.dsc.client.task.TaskManagerException}

[Former Community Member]

I've restored the submit service and continue to get the same error, i.e. ALC-WKS-007-043. I'm using a required xfaform variable for both input and output.



This is the last portion of the latest server log:



2007-12-20 15:28:11,437 INFO [STDOUT] [Flex] [ERROR] Error handling message: flex.messaging.MessageException: com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@ce10a9 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)

operation = submitWithPriorData

clientId = 16801B9D-5F0D-33F4-6E41-FF5BCBA6053B

destination = task-actions

messageId = 72779A30-E176-CD61-A76F-F93CFE0F7862

timestamp = 1198182491343

timeToLive = 1198182491343

body = null

hdr(DSEndpoint) = workspace-polling-amf

hdr(DSId) = 167E70D8-711D-C602-90BC-109C9C1D389A

errorReply: Flex Message (flex.messaging.messages.ErrorMessage)

clientId = 16801B9D-5F0D-33F4-6E41-FF5BCBA6053B

correlationId = 72779A30-E176-CD61-A76F-F93CFE0F7862

destination = task-actions

messageId = 16801C82-DD0F-1BAF-14DB-CA88A3001D52

timestamp = 1198182491437

timeToLive = 0

body = null

code = Server.Processing

message = com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@ce10a9 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

details = null

rootCause = ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@ce10a9 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

body = null

extendedData = null

2007-12-20 15:28:11,453 INFO [STDOUT] [Flex] Error handling message: flex.messaging.MessageException: com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@ce10a9 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)

operation = submitWithPriorData

clientId = 16801B9D-5F0D-33F4-6E41-FF5BCBA6053B

destination = task-actions

messageId = 72779A30-E176-CD61-A76F-F93CFE0F7862

timestamp = 1198182491343

timeToLive = 1198182491343

body = null

hdr(DSEndpoint) = workspace-polling-amf

hdr(DSId) = 167E70D8-711D-C602-90BC-109C9C1D389A

errorReply: Flex Message (flex.messaging.messages.ErrorMessage)

clientId = 16801B9D-5F0D-33F4-6E41-FF5BCBA6053B

correlationId = 72779A30-E176-CD61-A76F-F93CFE0F7862

destination = task-actions

messageId = 16801C82-DD0F-1BAF-14DB-CA88A3001D52

timestamp = 1198182491437

timeToLive = 0

body = null

code = Server.Processing

message = com.adobe.idp.dsc.util.InvalidCoercionException : Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@ce10a9 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

details = null

rootCause = ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance@ce10a9 of type: com.adobe.idp.taskmanager.form.impl.xfa.XFARepositoryFormInstance to type: class com.adobe.idp.Document

body = null

extendedData = null

2007-12-20 15:28:26,265 ERROR [org.jgroups.protocols.UDP] exception=java.net.NoRouteToHostException: No route to host: Datagram send failed, msg=[dst: 238.83.151.175:42296, src: tbwlivecycle01:3609 (3 headers), size = 0 bytes], mcast_addr=238.83.151.175:42296

2007-12-20 15:28:28,312 ERROR [org.jgroups.protocols.UDP] exception=java.net.NoRouteToHostException: No route to host: Datagram send failed, msg=[dst: 238.83.151.175:42296, src: tbwlivecycle01:3609 (3 headers), size = 0 bytes], mcast_addr=238.83.151.175:42296



Thanks!

[Jasmin_Charbonn]

Let's continue the discussion on that post http://www.adobeforums.com/webx/.3c059b98/4



since I think this is the same issue.



Jasmin