I am introducing here Quote to Cash which is well known as QTC. QTC is a process where Sales Organizations send details to their customers on their product offerings as per their need, provide them with the pricing for the set of products that they have requested, put all those in an official document called Quote and then it continues through Invoice, payment and negotiation which comes under Cash.
Any code when written in a clean, easy to understand and formatted way is easily readable and accepted by everyone.
It is essential for everyone to easily understand the code one writes as the same projects can involve the participation of multiple programmers. For easy identification and understanding of the code and code flow by everyone involved, it is essential that the code is structured, clean, and easily maintainable.
Explained below are some of the practices to write clean and understandable code.
Commenting and Documentation
For any software project reliable documentation is crucial. Commenting and documentation help one analyze what’s happening inside the code. This is very crucial for the one who is examining the code for the very first time. Writing comments for methods or functions is good for understanding its purpose. They can quickly show what a complex function is doing.Continue reading
Salesforce.com has been the number one CRM platform for some time now and its accomplishments as a CRM solution can be described as none less than the top of the line. But there are some common issues that all the CRM systems face and which is prevalent in Salesforce as well. Managing Data duplicity is one such big issue.Continue reading
In order to create a jira custom field type, you should be aware of basic plugin development.
Please follow the following steps to create an advanced jira custom field.
Create a basic Jira plugin skeleton. For creating Jira Plugin please refer to the given link https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project/create-a-helloworld-plugin-project
After creating a Basic plugin skeleton modify your atlassian-plugin.xml and add the following code in your atlassian-plugin.xml. Continue reading
As the name suggests, It is an error of View State. The maximum view state size limit (135KB) exceeded is the error message pertaining to View State error in salesforce and here follows a brief detailing of the issue.
View state error in salesforce holds the state/size of the visual force page that includes the components, field values, and controller state. This is important in the light that salesforce provides only a standard size of 135kb for any individual page. If the size of a particular page exceeds 135kb, the page will throw a view state error.Continue reading
The following piece of code when executed, helps us move jira migrate attachments between two issues of same project or different projects in Jira.
Here I have two issues, one of them will be the source issue, where user adds jira copy attachements to another issue will be the target issue, where the user want to move the attachment to.
This functionality is working fine in JIRA in its UI, however, I have tried to accomplish the same functionality through Java code. The following code executes the task of moving an attachment between the issues of both same or different projects.
Time-based workflow is an automated process to implement the business logic, that evaluates the record at the time of creation or update. It is one of the most powerful tools of Salesforce.
Workflow becomes indispensable to organizations for maximizing efficiency in their business processes. It allows tracking of processes.
Time-dependent workflow has the following actions:-
Jira provides the ability to display information about project/issues/data on a dashboard, through the use of gadgets. Gadgets XML are a big leap in JIRA reporting features.
In this document here I shall give instructions on how to write your first Jira gadget.
For administrators working with a single company, change sets are a great way to move updates between sandboxes and a parent org. However, when working on the enterprise tier, we often need to transfer components between various test and developer environments, which are outside the scope of change sets.
To support multiple developers working across multiple environments on various features and fixes, a proven path is to use an automated continuous integration system to simplify deployments and promote transparency.Continue reading