Automic Workload Automation

  • 1.  Notification size limits

    Posted Aug 15, 2014 11:02 AM

    I know that strings are limited to 1023 characters, and this is causing some headaches when building html tables dynamically in the notification jobs. However I have managed to do it.  The problem I am now facing is that when I got the tables working correctly I thought it would be nice to add in some hyperlinks to documents that were being referenced.  This also works on one hyperlink for testing, but when I went to complete the table with hyperlinks I began getting 1023 character errors.  The place that it is telling me to look doesn't make sense because the variable has already been restricted to 600 characters, so I am thinking that the Notification body text is limited and UC4 has no way of saying this other than to point to the last variable used in the body. Is this accurate?  Is the text of a notification limited to 1023 characters as well?   It would be really sad if this is true.



  • 2.  Notification size limits

    Posted Aug 15, 2014 12:09 PM

    I'm on V8 OM so I don't have any direct experience with this issue though we do include links in our notification text.  However, the Notification object's Notification tab documentation for V10.2 states:

     

    Text field for the message
    Max. 8000 characters. This field allows text and Variable objects, but if you want to create anything more complex (like returning the calling object’s name or putting in a line break), you will want to use the Process tab instead. This setting is ignored if you use the Process tab.

    Hope this helps a bit.

    p.s. string type variables are limited to 1024 characters, not 1023, not that that is possibly related to your issue.  Hey, what's one character among friends?  ;)




  • 3.  Notification size limits

    Posted Aug 15, 2014 12:39 PM

    @Mark Hadler   I am on Automation Engine V9 which tells you the String Character limit is 1023. It might just be the way they count that gives you 1 number difference but still the same size.  Kind of like how they start their arrays at 1 instead of 0.  

    8/15/2014 11:02:45 AM -  U1001323 The maximum record length of 1023 characters was exceeded.

    This is the full error that I receive.


    8/15/2014 11:37:04 AM -  U0020381 Runtime error in object 'FHR.CALL.PATCHING_EMAIL_THREAD', line '00003': See prior message!

    8/15/2014 11:37:04 AM -  U0011000 'FHR.CALL.PATCHING_EMAIL_THREAD' (RunID: '0139343950') could not be started on 'NON_PROD#WP004'. See next message.

    8/15/2014 11:37:04 AM -  U0020381 Runtime error in object 'FHR.CALL.PATCHING_EMAIL_THREAD', line '00003': See prior message!

     

    8/15/2014 11:37:03 AM -  U1001323 The maximum record length of 1023 characters was exceeded.

    The weirdest part of this message is that there is nothing in the process tab and no line 3 of the object.  



  • 4.  Notification size limits

    Posted Aug 15, 2014 01:16 PM

    Hmm, there is this regarding theU1001323message.  Did you check the length of the full variable once all subsititution occurs?  For example if you are doing something like the following -

    :SET &words = "lots and lots of characters."
    :SET &some_var = "Lots of words. And even more &words."

    and it is the last SET that fails since the result would exceed the 1024 or 1023 limit.

    Updated to include actual link, I just did a search for the U1001323 in the Search window on the Service Now Home page. 

    https://uc4.service-now.com/ess/main_content.do?sysparm_search=U1001323



  • 5.  Notification size limits

    Posted Aug 15, 2014 01:32 PM

    This is the length of the all the message body variables

    2014-08-15 11:37:02 - U0020408 body1: 0000000000000720

    2014-08-15 11:37:02 - U0020408 body2: 0000000000000724

    2014-08-15 11:37:02 - U0020408 body3: 0000000000000720

    2014-08-15 11:37:02 - U0020408 body4: 0000000000000970

    2014-08-15 11:37:02 - U0020408 body5: 0000000000000684

    2014-08-15 11:37:02 - U0020408 body6: 0000000000000677

    2014-08-15 11:37:02 - U0020408 body7: 0000000000000678



    And the link didn't work



  • 6.  Notification size limits

    Posted Aug 15, 2014 01:49 PM

    I updated the link in my previous reply.

    Have you tried manually executing the object with an activation protocol (Execute Once, Test options) to see which statement is failing?



  • 7.  Notification size limits

    Posted Aug 18, 2014 10:22 AM
    Yes.  But this only shows that there is nothing wrong with the variables in the sql job.  The problem is with the Notification.  It continues to say Line 3 Maximum Record of Length.  This isnt helpful since there is nothing in the Notification Process tab.  I am certain this is UC4 puking an error that it doesn't know how to articulate, that is related to exceeding the max size of email.   Both the String Var limit and Notification Limit should be much larger.

     



  • 8.  Notification size limits

    Posted Aug 18, 2014 11:05 AM

    Well then I'd suggest opening an incident with support.

    Sorry I can't be of more assistance.



  • 9.  Notification size limits

    Posted Aug 18, 2014 11:33 AM
    Thanks.