default value of a text field

Hi,
Is there a way to set a default value for a text field in a CRF? I see there is an option to set this for ‘Single-Select’ response type. I am hoping to have a URL item in a CRF, that will differ only at their ends. I’s hoping, I could get the ‘common’ part as default text, to which the user can append. Is it possible?
Thanks,
Suresh
Email Disclaimer: www.stjude.org/emaildisclaimer

Comments

  • GerbenRienkGerbenRienk Posts: 789 ✭✭✭
    Hi Suresh,
    Yes that's possible: see the attached CRF.
    I added a regular expression to make sure the users do not delete the
    default part.
    Hope this helps,
    Gerben Rienk
    > > Hi,
    > >
    > > Is there a way to set a default value for a text field in a CRF? I see
    > > there is an option to set this for 'Single-Select' response type. I am
    > > hoping to have a URL item in a CRF, that will differ only at their ends.
    > > I's hoping, I could get the 'common' part as default text, to which the
    > > user can append. Is it possible?
    > >
    > > Thanks,
    > >
    > > Suresh
    > >
    > >
    > > _____
    > >
    > > Email Disclaimer: www.stjude.org/emaildisclaimer
    > >
    > >
    Attachments:
    DefaultURL.zip 15.3 KB
  • suresh.tsuresh.t Posts: 44
    Thank you, Gerben. I should have at least tried this before posting the question. I read in the instructions, more than what had been stated (as if this is only applicable to SINGLE-SELECT). Thank you, again.
    Suresh
    -----Original Message-----
    Sent: Wednesday, April 25, 2012 1:40 PM
    To: [email protected]
    Subject: Re: [Users] default value of a text field
    Hi Suresh,
    Yes that's possible: see the attached CRF.
    I added a regular expression to make sure the users do not delete the default part.
    Hope this helps,
    Gerben Rienk
    > > Hi,
    > >
    > > Is there a way to set a default value for a text field in a CRF? I
    > > see there is an option to set this for 'Single-Select' response type.
    > > I am hoping to have a URL item in a CRF, that will differ only at their ends.
    > > I's hoping, I could get the 'common' part as default text, to which
    > > the user can append. Is it possible?
    > >
    > > Thanks,
    > >
    > > Suresh
    > >
    > >
    > > _____
    > >
    > > Email Disclaimer: www.stjude.org/emaildisclaimer
    > >
    > >
  • ccollinsccollins Posts: 376 admin
    Gerben and Suresh,
    Glad the problem was solved. I've added Suresh's observation about the
    default values instructions to a general ticket for improving the CRF
    instructions documentation in 3.1.3:
    https://issuetracker.openclinica.com/view.php?id=13769
    Cal
    -----Original Message-----
    [mailto:[email protected]] On Behalf Of Thiagarajan, Suresh
    Sent: Wednesday, April 25, 2012 2:53 PM
    To: '[email protected]'
    Subject: Re: [Users] default value of a text field
    Thank you, Gerben. I should have at least tried this before posting the
    question. I read in the instructions, more than what had been stated
    (as if this is only applicable to SINGLE-SELECT). Thank you, again.
    Suresh
    -----Original Message-----
    [mailto:[email protected]] On Behalf Of Gerben Rienk
    Sent: Wednesday, April 25, 2012 1:40 PM
    To: [email protected]
    Subject: Re: [Users] default value of a text field
    Hi Suresh,
    Yes that's possible: see the attached CRF.
    I added a regular expression to make sure the users do not delete the
    default part.
    Hope this helps,
    Gerben Rienk
    > > Hi,
    > >
    > > Is there a way to set a default value for a text field in a CRF? I
    > > see there is an option to set this for 'Single-Select' response type.
    > > I am hoping to have a URL item in a CRF, that will differ only at
    their ends.
    > > I's hoping, I could get the 'common' part as default text, to which
    > > the user can append. Is it possible?
    > >
    > > Thanks,
    > >
    > > Suresh
    > >
    > >
    > > _____
    > >
    > > Email Disclaimer: www.stjude.org/emaildisclaimer
    > >
    > >
This discussion has been closed.