Skip to main content

#Case Origin토론 중인 항목 0개

Akash Bhosale (Analog) 님이 * Trailhead Official *에 질문했습니다

Hi,

 

I have implemented a web-to-form in my website, and it is working fine, creating leads. However, I have a couple of doubts.

 

Question 1: I want to insert a default value for the case origin field from the web form itself and not use the default web origin option from settings.

 

Question 2: The case origin field is a standard required field. When I am creating cases from the web, it is creating them without the case origin, which is a required field. When I try to create a case from the org without filling in the case origin, I am not able to do it. What is the reason for this?

 

#Web-to-Case #Case Origin

답변 7개
  1. 2024년 3월 15일 오전 5:49

    Hi @Akash Bhosale

    In web-to-case form if you observe all the Values for Name are in camel case(lowerCase),

    for example

     

    <label for="name">Contact Name</label><input  id="name" maxlength="80" name="name" size="20" type="text" /><br>

    <label for="email">Email</label><input  id="email" maxlength="80" name="email" size="20" type="text" /><br>

     

    we only have fields that have a single name if we had a field that has long name like CaseAssignee in the web-to-case form it would have been shown as caseAssignee.

     

    and this is something that you cannot change it comes pre-defined by salesforce when you generate web-to-case html

     

    <label for="email">Email</label><input  id="email" maxlength="80" name="email" size="20" type="text" /><br>

     

    in the above tag if you change name="Email" it will not work, we should not change the value

     

    it is a Web Coding Standard followed in HTML form, that's the reason Origin will not work unless its origin

    it is considered a best practice to use lowercase letters in HTML code to improve readability and avoid potential errors

0/9000

Today the Global Action setting we have for Snapins Chat PreChat quick action managed to reset itself from Case Origin = Chat to Case Origin = Web.  It has done this in the past and we don't know why.  It happened at almost the same time as the Service Degradation issue for our org was resolved.  Has anyone else had this happen?  Do you think the timing was coincidental or could this have been caused by the service degradation problem?

댓글 5개
0/9000