The only purpose of this component is to find a record (through a series of picklist values) and return the matching record from the list when the button is clicked (there's only going to be one record always).
The component should be able to get the record ID and pass it on to the page where the component is used.
The vf page where the controller is used uses another controller.
1. How can I pass the record ID found in the component to the page's controller without using a URL parameter? I do not want the ID to be seen in the URL where it can be edited or removed.
2. To make the vfp reusable, what code should I use so that the PageReference value is dynamic instead of hardcoding the actual page names where the ID will be used?
I'm still trying to learn a lot from Apex/VFP but if anyone could point to the right direction it would be very helpful.
I'm looking for a suggestion or a better way that we can implement this requirement:
We have a picklist of our products and they will be displayed on a customer facing visualforce page with a "next" button. Let's say the picklist values are:
Product A
Product B
Product C
Product A is the most recent version and therefore we wanted to display a 'premium' content page when the "Next" is clicked. Products B and C are considered obsolete will go to another page that is more of a common page than what Product A has.
Now, this is not a problem to simply redirect to a different page based on the picklist value, we can use JS to accomplish that or rendered outputpanels.
Our challenge is to make this scallable since Product A may become obsolete in the future and we will add another product in the list (say, Product X)
What we dont want to end up with is to edit the pages every time we release a new product just in order to redirect it to the premium page. Not to mention doing this for multiple "latest version" products in different product lines.
Is there a way that we could tag particular products (using maybe another field) and just use that to reference in our pages to display our premium pages? The goal is to have something that we can edit in the object level (for us it's Case) rather than edit the visualforce pages every time we launch a new product.
I am new to writing triggers (in fact, havent written anything yet) but I am fairly familiar with custom controllers and visualforce pages.
recently we have a requirement to count the number of cases related to an asset. There's already a built-in relationship and the detail page of the asset displays the number of cases in one of the links at the top "Cases [1]".
I'm wondering how I can put this number in a custom number field so we can run our own asset validations through this field?
Any help in getting started is greatly appreciated.
We're have written an apex controller for vfp and the test coverage is 100%. However the average across all class/trigger is only at 55% because of some Triggers pulling it down. Is there a way we could exclude these triggers from being fired in our test class?
We are trying to create a w2c form with the ability to attach an asset to the case being generated.
We have an external system that imports assets and it generates a unique code. What we'd like to do is for the customer to enter that unique code in the form, find the asset, get the ID, then be able to submit a w2c.
We are able to run a query and display the asset in a vfp page but we are unable to attach the asset to the case itself. There is only one asset field in the case object and that is a lookup which we dont want to display on the page as this requires end-user searching through a list of records.
I'm wondering whether it is possible to assign the asset before the case gets inserted (in the custom controller) and if so, what are the fields in involve?
The only purpose of this component is to find a record (through a series of picklist values) and return the matching record from the list when the button is clicked (there's only going to be one record always).
The component should be able to get the record ID and pass it on to the page where the component is used.
The vf page where the controller is used uses another controller.
1. How can I pass the record ID found in the component to the page's controller without using a URL parameter? I do not want the ID to be seen in the URL where it can be edited or removed.
2. To make the vfp reusable, what code should I use so that the PageReference value is dynamic instead of hardcoding the actual page names where the ID will be used?
I'm still trying to learn a lot from Apex/VFP but if anyone could point to the right direction it would be very helpful.
I'm looking for a suggestion or a better way that we can implement this requirement:
We have a picklist of our products and they will be displayed on a customer facing visualforce page with a "next" button. Let's say the picklist values are:
Product A
Product B
Product C
Product A is the most recent version and therefore we wanted to display a 'premium' content page when the "Next" is clicked. Products B and C are considered obsolete will go to another page that is more of a common page than what Product A has.
Now, this is not a problem to simply redirect to a different page based on the picklist value, we can use JS to accomplish that or rendered outputpanels.
Our challenge is to make this scallable since Product A may become obsolete in the future and we will add another product in the list (say, Product X)
What we dont want to end up with is to edit the pages every time we release a new product just in order to redirect it to the premium page. Not to mention doing this for multiple "latest version" products in different product lines.
Is there a way that we could tag particular products (using maybe another field) and just use that to reference in our pages to display our premium pages? The goal is to have something that we can edit in the object level (for us it's Case) rather than edit the visualforce pages every time we launch a new product.
We're have written an apex controller for vfp and the test coverage is 100%. However the average across all class/trigger is only at 55% because of some Triggers pulling it down. Is there a way we could exclude these triggers from being fired in our test class?
Recently I was working on a requirement which required overriding the Case detail page with a visualforce page. Problem crept when the related list comonent didnt worked for Case Comments and History. So I decided to write my own code to display the related lists.
I was finally able to write my own code to display the related list. It implements all the function that standard related list of Case Comments provide. In order to make it reusable, I made it as a component so that in other pages I just need to pass the Case Id and I will get the complete list of Case Comments.
Heres the code finally :
1. Component Code
<apex:component controller="CaseCommentsComponentController" allowDML="true"> <!-- Attribute Definition --> <apex:attribute name="CaseId" description="Salesforce Id of the Case whose Case Comments needs to be rendered" type="Id" required="true" assignTo="{!caseId}" />
public with sharing class CaseCommentsComponentController {
public Id caseId {get; set;} public cComments[] comments{ get{ List<cComments> comments = new List<cComments>(); for(CaseComment comment : [Select LastModifiedDate, LastModifiedBy.Id, LastModifiedBy.Name, IsPublished, CreatedDate, CreatedBy.Id, CreatedBy.Name, CommentBody From CaseComment c where ParentId = :caseId order by c.LastModifiedDate desc]) { cComments tempcComment = new cComments(); tempcComment.cComment = comment;
