Idea Details

Character limit

Last activity 06-13-2019 10:11 AM
Anon Anon's profile image
12-05-2013 08:35 PM

@Idea #1


1024 characters maximum for actions.  For example, adding text & replacing text - we have config files that need to be generated that are small but still don’t fit the Nolio max number of characters.  Would be great if Nolio had more flexibility for large text files


Annoyance #2


256 characters maximum for sdtout/stderr – need to output log files to filesystem or repository.  Would be great if Nolio was more flexible about stdout and stderr.  Output of up to 10 to 20 MB should be allowed if that doesn’t disturb the performance too much. .  I understand that over time the DB would get bloated, but we should be able to set a retention policy of various types of objects upon creating or modifying each “Nolio application”, like we can for TFS Builds :


04-18-2016 07:14 PM


We have increase the length of the sting parameter, which can be used as action input, to 10k characters in version 6.1 which was released in April, 2016.



Nofar Bluestein

Principal Product Manager, Release Automation, NA

01-22-2016 10:04 PM

Je suis absent(e) du bureau jusqu'au 28/01/2016


Veuillez contacter SVP : G2S DPRO EXPL SYS MEDIA OPEN



Remarque : ceci est une réponse automatique à votre message  "Re: [CA

Release Automation] - Character limit" envoyé le 22/01/2016 22:24:25.


C'est la seule notification que vous recevrez pendant l'absence de cette


01-22-2016 04:23 PM


We have decided to increase the length of the sting parameter, which can be used as action input, to 10k characters, rather than the current 1k. It will be a part of RA v5.6 , which will be GA on March 25th, 2016.



Nofar Bluestein

Principal Product Manager, Release Automation, NA

09-03-2015 02:12 AM

You may have a look to idea Collecting application specific deployment logs

This issues the logging in a more general way. Please vote for this to get a good solution implemented in RA

01-28-2015 04:21 PM

A sophisticated logging mechanism where the complete output stdout/stderr of an action can be stored on a specific logging server is essential.The output larger than 256 char is thrown away. If the action is completing successfully i might not bother but if the action is failing i need to know the complete output. This is essential for traceability.


There should be a global setting on application level to define on which server the ouput of all actions should be stored.

01-05-2015 07:33 AM

There're 1024 character limit in Powershell action pack too on the script block. Will be good if we could remove the constrain.

10-28-2014 09:17 AM

Just an FYI I had previously entered the community idea "Remove 256-char limit on Run Command Std Out Output to Param" so it is entered separately if that is needed for it to be considered. Thank you!

10-28-2014 05:20 AM

For file path and parameter value I will try to align it to a value of 1024 or 512 characters. As I have seen when we are accessing something from svn or http external source code repository with hierarchy the path easily crosses 500 char limit.

10-28-2014 04:42 AM

dr.richard.chester jaisa05, can share with us the reasonable limit we should support?

08-25-2014 08:21 AM

Jacky_Mahadab is correct. we will solve it in the UI as well

07-30-2014 12:25 PM

Just note that this limitation is only relevant when creating/modifying Artifact via ROC.

When creating Artifact using actions you don't have this limitation

07-30-2014 11:20 AM

Hi Uri,

the restriction is find on 5.0 interface of ROC when trying to enter the artifact path which currently doesn't allows to enter more than 100 characters

07-30-2014 10:31 AM

Hi Richard - when do you have this limit? in the Artifact version?

07-17-2014 03:16 PM

Indeed this means that the limit of 1024 charcter is only confined to entering parameters value via UI. So parameters can stil hold longer value then this if set either from file or by concatenation.

07-14-2014 06:16 AM

The 3rd parameter will include both parameters values , the 1024 characters limit is enforce on the UI only and not on the actual  parameter size , If you will add the value of the 3rd parameter into file  , (e.g using add text to file action) you will see all characters

07-14-2014 05:02 AM

What is the behavior at application level when I append the value of two parameters each having 1000 chars and assign it to 3rd parameter which will now hold 2000 characters.

We have a block from the UI only where we throw warning of 1024 characters.

07-09-2014 10:42 AM

Artifact Full Path Restriction - this is restricted to 99 chars, it seems reasonable to have more chars for a file path, 99 is not especially long. There is a limit in windows, surely that would be a better limit?

06-24-2014 04:18 AM

The limit is not per input. it is per parameter. if you have multiple parameters together, you can have a larger size. when you state a 'concrete' value, the size is much larger

03-07-2014 11:19 AM

256 characters maximum for sdtout/stderr
A lot of output can be generated by steps, especially scripts - and the ability to see more than a single line of output with the process results is sorely missing.