Customer Portal

Get Involved. Join the Conversation.

Comments

  • Clinton Messias

    Do I need to use  <rn:condition>?  Is necessary? Or I can delete and work without it

    And this is the default version, right?

    I will copy it and test

  • Sebastiaan Draaisma

    I never worked with bootstrap so I can't really comment on that part but you had a lot of scripts.

    The out of the box version is only 26 lines :-)

    <rn:meta title="#rn:msg:ASK_QUESTION_HDG#" template="standard.php" clickstream="incident_create"/>
     
     <div id="rn_PageTitle" class="rn_AskQuestion">
      <!-- <h1>#rn:msg:SUBMIT_QUESTION_OUR_SUPPORT_TEAM_CMD#</h1> -->
    </div
    <div id="rn_PageContent" class="rn_AskQuestion">
        <div class="rn_Padding">
            <form id="rn_QuestionSubmit" method="post" action="/ci/ajaxRequest/sendForm">
                <div id="rn_ErrorLocation"></div>
                <rn:condition logged_in="false">
                    <rn:widget path="input/FormInput" name="Contact.Emails.PRIMARY.Address" required="true" initial_focus="true" label_input="#rn:msg:EMAIL_ADDR_LBL#"/>
                    <rn:widget path="input/FormInput" name="Incident.Subject" required="true" label_input="#rn:msg:SUBJECT_LBL#"/>
                </rn:condition>
                <rn:condition logged_in="true">
                    <rn:widget path="input/FormInput" name="Incident.Subject" required="true" initial_focus="true" label_input="#rn:msg:SUBJECT_LBL#"/>
                </rn:condition>
                    <rn:widget path="input/FormInput" name="Incident.Threads" required="true" label_input="#rn:msg:QUESTION_LBL#"/>
                    <rn:widget path="input/FileAttachmentUpload"/>
                    <rn:widget path="input/ProductCategoryInput"/>
                    <!--rn:widget path="input/ProductCategoryInput" data_type="Category"/-->
                    <rn:widget path="input/CustomAllInput" table="Incident"/>
                    <rn:widget path="input/FormSubmit" label_button="#rn:msg:CONTINUE_ELLIPSIS_CMD#" on_success_url="/app/ask_confirm" error_location="rn_ErrorLocation"/>
                    <rn:widget path="input/SmartAssistantDialog"/>
            </form>
        </div>
    </div>
  • Clinton Messias

    I did it

    I comment one by one and when I add any Incident field show this error (when I click in submit), if I leave only contact field in form, the submit button work normally.

    I will delete and create the all Incident fields and try again.

    Thank you

  • Sebastiaan Draaisma

    While I was unable to spot something immediately, my best advice for troubleshooting is to comment major sections out one by one until you identify the section causing the conflict. After that you can refine the section into smaller sections until you are able to pinpoint the issue.

    Not much help for now I'm afraid but someone else here may be able to spot the issue :-)

  • Clinton Messias

    Wow, Sorry ^^

    ask.php (18KB)
  • Sebastiaan Draaisma

    Hi Clinton

    I admit getting older but I don't see any attachment laugh

  • Clinton Messias

    Hello Sebastiaan,

     

    • Are you able to attach the ask.php then we can check if the code contains mistakes or is missing something Yes, I can do it
    • Are you able to see your custom fields? If not check the visibility settings in your custom field editor Yes, I can see the custom field in CP
    • Also check in which environment you are looking at the site (Development, Stage, Production) I'm seeing in the development site, I'm making all the changes first and testing before.

    Follow the ask.php in the attachment.

     

    Ps: Exist any scripts and CSS embedded in ask.php, I will make all the changes and so separate this scripts ^^ 

     

    Thank you

  • Cosimo Galasso

    I the controller you should manage all of those operations .. create the incidents and then the attach to it the secondary contacts.

    First look at the standard model class if they can be used, otherwise create your own custom model.

    CG

  • Sebastiaan Draaisma

    Hi Clinton.

    A few questions :-)

    • Are you able to attach the ask.php then we can check if the code contains mistakes or is missing something
    • Are you able to see your custom fields? If not check the visibility settings in your custom field editor
    • Also check in which environment you are looking at the site (Development, Stage, Production)
  • Craig chevey@solihull.gov.uk

    Excellent...however, does this mean that I will also need to now additionally get a PaaS license subscription/credits on top of my OSvC subscription in order to use VBCS for Customer Portal?

    When I originally moved from EBS TeleService to Service Cloud we had access to Oracle Tap included which met our mobile needs. This then got removed, we were advised a mobile accelerator was available but we would need to additionally license Mobile Cloud Service at a substantial cost to allow us to deploy! If I have to license VBCS at substantial additional cost then this won't really help.

  • Cosimo Galasso

    Have you considered to use the OSvC Outreach module?

    CG

  • Cosimo Galasso

    In your scenario it should be enough to unselect the option "Can Assign to Group".

    I did a quick test and in my test environment it's working as expected.

     

    CG

  • shuvan sarkar

    Thank you for your comment. I have tried two below thing:

    1. Can Assign to Group - Unselect this check box but still  staff members can assign the record to a parent group.

    2. Create workspace rule to exclude parent group from assigned field selection but It excluded all group except the own group. Still staff member can select won group in the assigned field. And good part is that staff member cannot select other parent group in the assigned field.I have mentioned one example in my previous comment.

  • Cosimo Galasso

    There are 2 options you can use in the incident workspace designer:

    1. Show Parent - Select this check box if you want the workspace to display the parent of the selected item (for example, a staff account’s group in the Assigned field)
    2. Can Assign to Group - Select this check box to permit staff members to assign the record to a group rather than a specific staff member. If this check box is not selected, staff members must assign the record to a staff member within a group.

    In addition to that you can use workspace rules to explicitly exclude/include specific items (pay attention in your rule it looks like you are including not excluding items).

    CG

  • Willie Eide

    For future updates you can access and subscribe to the answer at cx.rightnow.com  https://cx.rightnow.com/app/answers/detail/a_id/10621 (Answer:10621) 

    By doing this you'd get advance notice of upcoming releases and what is contained in those releases.

    Stay Informed!