peterknolle.com Report : Visit Site

Technical data of the peterknolle.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host peterknolle.com. Currently, hosted in United States and its service provider is Athenix Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called nginx/1.14.0 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

skip to content peter knolle salesforce and software development technical articles apexless lightning components january 27, 2018 january 27, 2018 peter knolle 9 comments a great deal can be done with custom lightning components without the need for any apex code. the lightning:inputfield component is designed to be used with the lightning:recordeditform to provide a quick and easy way to edit records without needing an apex controller and can be combined with force:recorddata for greater flexibility. additionally, there are declarative/configuration features of lightning components and app builder that can be added into the mix to provide powerful functionality that may have previously required apex code. this post explores the combination of all of those with a custom lightning component that uses no apex code. quick side note rené winkelmeyer ( @muenzpraeger ) wrote a similar post on the salesforce developer’s blog , including a good example with explanations of lightning:outputfield and lightning:recordviewform as well and the benefits of using input/outputfield (fls, labels, type handling, etc.). please refer to that and the lightning components developer guide for more information. the component the component is an sla component (sla.cmp) that is designed to appear on record home pages for selected objects related to the account object. if the sla is near expiration or expired, the component appears for the user to update. if it is not expired or not near expiration, it does not appear. object restriction and field configuration before we look at the code, let’s look at how we can support the usage of the component for selected objects related to the account. the component design file (sla.design) is as follows: sla.design xhtml <design:component label="sla"> <design:attribute name="accountlookupapiname" label="acccount lookup api name" description="api name of the lookup field to the account" /> <sfdc:objects> <sfdc:object>contact</sfdc:object> <sfdc:object>case</sfdc:object> <sfdc:objec>my_object__c</sfdc:object> </sfdc:objects> </design:component> 1 2 3 4 5 6 7 8 9 10 <design:component label = "sla" > <design:attribute name = "accountlookupapiname" label = "acccount lookup api name" description = "api name of the lookup field to the account" /> <sfdc:objects> <sfdc:object> contact </sfdc:object> <sfdc:object> case </sfdc:object> <sfdc:objec> my_object__c </sfdc:object> </sfdc:objects> </design:component> the sfdc:objects element supports limiting the objects whose record home pages may have the component added to them. the component will only show up in the app builder component sidebar for those objects in the design file. for example, it will not show up in the opportunity record home page in the app builder. note if there is nothing specified it is available for all. the accountlookupapiname design:attribute is used to dynamically get the id or the related account. if added to the case page, the page configurer would specify accountid, if added to a custom object they might specify account__c, or whatever their custom api name is. conditional rendering another requirement is that the component should only show when the sla is expired or nearing expiration. this can be done 100% declarativey within the app builder with a component visibility filter. there are a couple of interesting things to note about the visibility filter. it has the ability to look up to parent fields much like formulas or soql queries. this one is referencing a checkbox field. although there is an sla date field, it cannot be used in the filter, because date types are not supported. the work around is to just create a checkbox formula field and reference that. there is a formula field sla_renewal_needed__c that is defined as slaexpirationdate__c < today() – 5. fields related to the current user, as opposed to the record, can also be added, so i could have added an additional filter to only show this component for a certain profile, for example. additionally, multiple conditions and conditional logic can be specified. once saved, the component hover on the page in the app builder shows a little orange eye icon in the upper right hand corner. the component code – lightning:recordeditform and lightning:inputfield the component is divided into two parts. one is responsible for getting the related account’s id from the record being viewed. the other is responsible for editing the sla information. the sla editing part has been abstracted into its own component (slaacct.cmp) as follows: slaacct.cmp xhtml <aura:component access="global" > <aura:attribute name="recordid" type="string" access="public"/> <div class="slds-page-header" role="banner"> <p class="slds-text-heading_label"> <lightning:icon iconname="utility:error" variant="error"/> the sla must be extended! </p> </div> <lightning:recordeditform recordid="{!v.recordid}" objectapiname="account"> <div class="slds-box slds-theme_default"> <lightning:messages /> <lightning:inputfield fieldname="sla__c"/> <lightning:inputfield fieldname="slaserialnumber__c"/> <lightning:inputfield fieldname="slaexpirationdate__c" /> <lightning:button class="slds-m-top_small" variant="brand" type="submit" name="update" label="update" /> </div> </lightning:recordeditform> </aura:component> 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 <aura:component access = "global" > <aura:attribute name = "recordid" type = "string" access = "public" /> <div class = "slds-page-header" role = "banner" > <p class = "slds-text-heading_label" > <lightning:icon iconname = "utility:error" variant = "error" /> the sla must be extended! </p> </div> <lightning:recordeditform recordid = "{!v.recordid}" objectapiname = "account" > <div class = "slds-box slds-theme_default" > <lightning:messages /> <lightning:inputfield fieldname = "sla__c" /> <lightning:inputfield fieldname = "slaserialnumber__c" /> <lightning:inputfield fieldname = "slaexpirationdate__c" /> <lightning:button class = "slds-m-top_small" variant = "brand" type = "submit" name = "update" label = "update" /> </div> </lightning:recordeditform> </aura:component> the id of the account is provided by the containing component (sla.cmp). the code is very straightforward. it uses the lightning:recordeditform to handle the load and save of the account fields specified in the lightning:inputfield components. the lightning:messages component is needed to display an error message. it is important to note that the declarative validations are handled completely without the need to write any javascript, just like visualforce. there are also event attributes for lightning:recordeditform (e.g., onload, onerror, onsubmit, onsuccess), for which you can provide event handlers to further customize the experience. if there is an error, the record will not be saved and an error will be displayed. the component code – force:recorddata the sla.cmp is the component that is available to drag and drop onto pages in the app builder, so it needs to be flexible enough to handle any api name for the account lookup. (note: this could be simplified greatly if the flexibility of any api name was not needed and it could be hardcoded as accountid, for example.) sla.cmp xhtml <aura:component implements="flexipage:availableforrecordhome,force:hasrecordid"> <aura:attribute name="accountlookupapiname" type="string" required="true" access="global"/> <aura:attribute name="fieldslist" type="string[]" /> <aura:attribute name="accountid" type="id" /> <aura:attribute name="sourcerecordfields" type="object"/> <aura:handler name="init" value="{!this}" action=

URL analysis for peterknolle.com

http://peterknolle.com/time-custom-field/
http://peterknolle.com/#content
http://peterknolle.com/automatic-lightning-styles-for-visualforce/
http://peterknolle.com/lightning-experience-time-switch/
http://peterknolle.com/apex-list-contains/
http://peterknolle.com/apexless-lightning-components/
http://peterknolle.com/page/2/
http://peterknolle.com/peter_knolle_resume.pdf
http://peterknolle.com/apexless-lightning-components/#comments
http://peterknolle.com/about
http://peterknolle.com/author/peter-knolle/
http://peterknolle.com/posts

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: PETERKNOLLE.COM
Registry Domain ID: 1837383221_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucowsdomains.com
Updated Date: 2017-11-14T09:01:44Z
Creation Date: 2013-11-30T03:19:14Z
Registry Expiry Date: 2020-11-30T03:19:14Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.ASMALLORANGE.COM
Name Server: NS2.ASMALLORANGE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-08-14T01:11:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR Tucows Domains Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =peterknolle.com

  PORT 43

  TYPE domain

DOMAIN

  NAME peterknolle.com

  CHANGED 2017-11-14

  CREATED 2013-11-30

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

NSERVER

  NS1.ASMALLORANGE.COM 67.228.207.194

  NS2.ASMALLORANGE.COM 67.19.36.196

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .