It is a method which runs on a separate thread in the background. It does not impact the performance of a running transaction as it carried out in a different context. We use this method for the execution of long running operation such as a web call out where we are not sure when the response will come or whether a response will come or not.<\/p>\n

This is not the only use case of the future method we also use them to isolate DML statement because there is a possibility that when two DML operation is performed over different sObject then we might get a mixed DML operation error. Future methods help us in preventing this error.<\/p>\n

<\/p>\n

Image: Depicting the difference in thread processing between apex normal transaction and in future method<\/p>\n

The specialty of the Future method is that it executes when the resources are available and does not out overhead on the server. This is the reason that execution of the code does not have to wait for the completion of a long running operation and also we get higher Governor limits when we use Asynchronous Apex.<\/p>\n

Simple syntax of the future method is mentioned below:<\/p>\n

Global class ClassNameOfFutureMethod<\/p>\n

{<\/p>\n

@Future<\/strong><\/p>\n

Public static void<\/strong> FuturemethoName()<\/p>\n

{<\/p>\n

\u00df Code to be executed \u00e0<\/p>\n

}<\/p>\n

}<\/p>\n

Some consideration before we start implementing the future method is that it should be declared as a static method and the only return type it can have is void. Secondly, the parameter defined for the future method must be primitive i.e. no salesforce sObject can be passed as a parameter to the future method. The reason an sObject is not passed in the future method is that there is a possibility that the sent sObject might change between the time the future method is executed.<\/p>\n

To interact future method with the sObject that already exists in the database, we can pass the ID of the object instead and then fetch the latest version of the record in the method itself and then perform the task, as shown below.<\/p>\n

global class ClassNameOfFutureMethod<\/p>\n

{<\/p>\n

\u00a0\u00a0\u00a0 @future<\/strong><\/p>\n

public static void<\/strong> FuturemethoName (List<ID> rIds)<\/p>\n

{<\/p>\n

\/\/ We can get the records based on the list of Ids<\/p>\n

List<custObj> obj = [SELECT Name FROM custObj WHERE Id IN : rIds];<\/p>\n

\/\/ We can Process records after fetching the records<\/p>\n

}<\/p>\n

}<\/p>\n

Below is a skeletal code of a future method that interacts with an external web service. For this we have to add an extra annotation to the method to make the platform aware that this method will interact with an external service, as shown below<\/p>\n

global class ClassNameOfFutureMethod<\/p>\n

{<\/p>\n

\u00a0\u00a0\u00a0 @future(callout=true)<\/strong><\/p>\n

public static void FuturemethoName (List<ID> rIds)<\/p>\n

{<\/p>\n

\/\/ We can get the records based on the list of Ids<\/p>\n

List<custObj> obj = [SELECT Name FROM custObj WHERE Id IN : rIds];<\/p>\n

\/\/ We can Process records after fetching the records<\/p>\n

}<\/p>\n

}<\/p>\n

Future methods are invoked as any other method in the apex, but a Future method cannot invoke another future method. There are certain limitations of the future methods in addition to the above-mentioned limitation which are given below:<\/p>\n

No more than 50 methods with Future annotation can be called in a single apex invocation.<\/p>\n

Maximum 250000 invocation is allowed per rolling 24-hours or number of licenses multiplied by 200 whichever is the greatest is the limit of the invocation. This limit is for the entire organization and is shared with the entire Asynchronous apex, i.e. Batch Apex, Queueable Apex and scheduled Apex.<\/p>\n

Testing Future Methods<\/h2>\n

Since Future method is called in different context then the running thread, it has to be tested in a different way than the normal. To make them run in the same context we make use of startTest() and stopTest() code block. All asynchronous method written after the startTest are collected by the system and are executed synchronously after the stopTest method is called, as shown below.<\/p>\n

@isTestprivate class ClassNameOfFutureMethodTest {\u00a0\u00a0\u00a0 @isTest static void test1() {\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Test.startTest();\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0ClassNameOfFutureMethod.FuturemethoName ();\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Test.stopTest();\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Verify the result with help of system.assertEquals\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }}<\/p>\n

Best practice and performance for Future method<\/h2>\n

Salesforce implements a queue based framework for the handling of the asynchronous processes, the queue is implied to balance the load of request across organizations, following are the best practice for the future methods:<\/p>\n

\n
1. Ensure fast execution of the of the future methods by tuning the query used in the method, the longer the future method takes to complete the execution the more delay occurs for the requests in the queue.<\/li>\n
2. Testing the future method to the maximum numbers of the result expected to handle, this will help in determining the delay<\/li>\n
3. Use batch apex if the number future method invocation is reasonably large. Avoid using a large number of future methods.<\/li>\n<\/ol>\n

   Next, we will discuss the Queueable Apex<\/p>\n

   Asynchronous Apex: Queueable Apex<\/h1>\n

   <\/p>\n

   Queueable Apex is also a way of running Apex jobs asynchronously and to make a class Queueable we need to implement an interface i.e. Queueable interface. With the help of this interface, we can queue jobs and also monitor them, this is an enhanced way of running the asynchronous process as compared to the future method.<\/p>\n

   Queueable jobs are similar to the future method as both are queued before the execution and get executed only after the resources are available, but the extra feature it offers is below:<\/p>\n

   \n
   1. An id is generated when the job is queued, with help of this Id one can monitor the progress of the job, from Salesforce UI or programmatically.<\/li>\n
   2. Non-primitive types are also allowed in these jobs, they can be accessed when the job is executed.<\/li>\n
   3. Chaining of the job is possible in Queueable apex, but it can call only chain one Queueable job<\/li>\n<\/ol>\n

      Queueable jobs implements the Queueable interface, in this interface we have an execute method which has return type of void and take QueueableContext as a parameter. Below is an example of implementation of the Apex Queueable job:<\/p>\n

      public class QueueableClass implements Queueable {<\/p>\n

      public void execute(QueueableContext context) {<\/p>\n

      contact con = new contact(lastName=’Datta’,Phone=’9999999999′);<\/p>\n

      insert con;<\/p>\n

      }<\/p>\n

      }<\/p>\n

      In order to add this class to the queue list, we need to make use of SystemEnqueueJob, these methods return an Id. With help of this Id, we can monitor its progress and check its status.<\/p>\n

      ID queuejobID = System.enqueueJob(new QueueableClass());<\/p>\n

      AsyncApexJob queuejobInfo = [SELECT Status,NumberOfErrors FROM AsyncApexJob WHERE Id=: queuejobID];<\/p>\n

      <\/p>\n

      Testing Queueable Jobs<\/h2>\n

      As we know that Queueable is an asynchronous job, therefore to test these classes we have to make use of the startTest and StopTest methods, where all the asynchronous method runs synchronously. Below is an example of the Queueable job and the way to test it.<\/p>\n

      @isTest<\/p>\n

      public class QueueableClass Test {<\/p>\n

      static testmethod void test1() {<\/p>\n

      Test.startTest();<\/p>\n

      System.enqueueJob(new AsyncExecutionExample());<\/p>\n

      Test.stopTest();<\/p>\n

      Contact con = [SELECT lastName,Phone FROM Contact WHERE lastName =’Datta’ LIMIT 1];<\/p>\n

      System.assertNotEquals(null, con);<\/p>\n

      System.assertEquals(‘9999999999’, con.Phone);<\/p>\n

      }<\/p>\n

      }<\/p>\n

      Chaining the Jobs<\/h2>\n

      There is a possibility that we want to perform a certain task after the completion of another job. As discussed before, we can call another Queueable Job from inside of a running queueable job. To do this we need to add another job to the queue in the execute method of the presently running job.\u00a0 We achieve this as shown below.<\/p>\n

      public class QueueableClass implements Queueable {<\/p>\n

      public void execute(QueueableContext context) {<\/p>\n

      contact con = new contact(lastName=’Datta’,Phone=’9999999999′);<\/p>\n

      insert con;<\/p>\n

      System.enqueueJob(new anotherQueueableJobClass());<\/p>\n

      }<\/p>\n

      }<\/p>\n

      Limitations of Queueable Jobs<\/h2>\n

      \n
      1. 50 jobs can be added to the queue with System.enqueueJob() method in a single transaction<\/li>\n
      2. Maximum depth of chain job is 5 i.e. 4 child jobs and initial parent job for Developer and Trail organizations but there is no limit in other editions<\/li>\n
      3. Only one job can be chained at a time, i.e. only one child job from the same Queueable job.<\/li>\n<\/ol>\n

         Now we will discuss Apex Scheduler<\/p>\n

         Asynchronous Apex:\u00a0Apex Scheduler<\/h1>\n

         To make a class invocable at a specific time, first, we need to implement Schedulable interface in the class and then schedule it either from Salesforce UI or from the system.schedule method.<\/p>\n

         Implementing the Interface schedulable<\/h2>\n

         To invoke a class on a regular basis we first need to implement the Schedulable interface, which like Queueable apex has an execute method. The scheduler run as system and user permission has no significance in executing the class.<\/p>\n

         As mentioned above, while implementing schedulable interface we need to implement the execute method of the interface which is a global method and takes schedulableContext as an argument, its syntax is given below.<\/p>\n

         global\u00a0void\u00a0execute(SchedulableContext\u00a0sc){}<\/p>\n

         This method is used to instantiate the class we want to schedule, as shown below.<\/p>\n

         global class MyScheduleClass implements Schedulable {<\/p>\n

         global void execute(SchedulableContext SC) {<\/p>\n

         Class2beSchedule M = new Class2beSchedule ();<\/p>\n

         }<\/p>\n

         }<\/p>\n

         The next method is used to schedule the class it is called system.schedule, as shown below.<\/p>\n

         MyScheduleClass m = new MyScheduleClass ();<\/p>\n

         String CronExpression = ’20 30 8 10 2 ?’;<\/p>\n

         String SchedulejobID = system.schedule(‘My Job’, CronExpression, m);<\/p>\n

         The schedulable class can also be used to Schedule a batch class, as shown below.<\/p>\n

         global class MyScheduleClass implements Schedulable {<\/p>\n

         global void execute(SchedulableContext SC) {<\/p>\n

         batchclass M = new batchclass ();<\/p>\n

         database.executeBatch(M);<\/p>\n

         }<\/p>\n

         }<\/p>\n

         Batch can also be schedule using the method system.schedulebatch, about this we will study in detail in later section.<\/p>\n

         Once the job is scheduled we can keep track of it with the help of schedulableContext, with help of its getTriggerID we can retrieve the Id of the scheduled job and we can query the CronTrigger Object and monitor the progress of the job.<\/p>\n

         To schedule a class we discussed that\u00a0 there are two ways:<\/p>\n

         \n
         1. From system UI<\/li>\n
         2. Using System.Schedule method<\/li>\n<\/ol>\n

            The difference between the two ways is that in the system.schedule method we can also specify the minutes and seconds as well but using the UI we can just mention the hour of the day.<\/p>\n

            Schematics of how to schedule a class from UI<\/p>\n

            Step 1:<\/p>\n

            <\/p>\n

            Step 2: To schedule weekly<\/p>\n

            <\/p>\n

            To Schedule Monthly<\/p>\n

            <\/p>\n

            Let’s discuss how to create a cron expression:<\/p>\n

            Basic syntax of cron expression is<\/p>\n

            S M H DOM Mon DOW Yr<\/p>\n

            S- Seconds<\/p>\n

            M- Minutes<\/p>\n

            H- Hour<\/p>\n

            DOM- Day_of_month<\/p>\n

            Mon- month<\/p>\n

            DOW-Day_of_week<\/p>\n

            Yr -Year<\/p>\n

            Then there are some special characters which are used in conjunction with the values like \u2018*\u2019, \u2018?\u2019, \u201c,\u201d,\u2019-\u2018<\/p>\n

            Some sample cron Expressions are mentioned below:<\/p>\n\n\n\n\n\n\n\n\n

            Expression<\/strong><\/td>\n	Description<\/strong><\/td>\n<\/tr>\n<\/thead>\n
            0 0 13 * * ?<\/td>\n	Class runs every day at 1 PM.<\/td>\n<\/tr>\n
            0 0 22 ? * 6L<\/td>\n	Class runs the last Friday of every month at 10 PM.<\/td>\n<\/tr>\n
            0 0 10 ? * MON-FRI<\/td>\n	Class runs Monday through Friday at 10 AM.<\/td>\n<\/tr>\n
            0 0 20 * * ? 2010<\/td>\n	Class runs every day at 8 PM during the year 2010.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Limitation of Apex Scheduler<\/h2>\n Following are the limitations of Apex Scheduler:<\/p>\n \n \n We can have only 100 apex scheduled jobs at one time in a particular Organization which can be checked and counted at scheduled jobs page in sSalesforce<\/ol>\n<\/li>\n<\/ol>\n \n They also count against the shared limit for the Asynchronous Apex i.e. 250000 for a rolling 24-hours period.<\/li>\n Extreme care has to be taken if the job is getting scheduled via Apex Trigger<\/li>\n Synchronous Web service callouts are not supported by the schedule Apex, to make call out we have to make use of the Asynchronous call out, however, a batch can job can be scheduled and callouts are supported from the batch<\/li>\n If a scheduled job is supposed to run during the maintenance downtime will be scheduled to execute after the maintenance work is completed.<\/li>\n<\/ol>\n Now let\u2019s shift our focus to batch class.<\/p>\n Asynchronous Apex:\u00a0Batch Class<\/h1>\n Salesforce Governor limits us to build a long running process like data cleansing or data archiving, where records more than 50000 are being processed at one time. To fulfill this requirement Salesforce has to introduce the batch Apex, a batch job makes smaller chunks of the data which is known as batch size and then asynchronously work on each batch in a separate thread and therefore not hitting the governor limit.<\/p>\n <\/p>\n ImageSource: https:\/\/i.stack.imgur.com\/7mHOq.png<\/a> How batch works<\/strong><\/p>\n A batch job can be invoked at runtime programmatically using apex and it can also be scheduled using a scheduled job as discussed above.<\/p>\n Using batch Apex<\/h2>\n A Class to be executed as a Batch has to implement the batchable interface. In this interface, we have to implement three methods, i.e Start, execute and finish methods.<\/p>\n <\/p>\n Image source: http:\/\/4.bp.blogspot.com\/-Cug5KaAx5Q4\/UkjTViCbSnI\/AAAAAAAAAFI\/r4ayS5iarrw\/s1600\/marketing-process-distribute1%5B2%5D.gif<\/a>\u00a0 Schematic of a Batch Class<\/p>\n To collect the records on which we have to perform the bulk processing tasks are collected in this method, this method returns an iterable or a Database.querylocator, both of the return types have their use cases but mostly Database.querylocator is used.<\/p>\n When a simple query is used to generate the collections of record, we should use database.querylocator. This object by passes the Salesforce governor limit of 50000 records and can return up to 50 million records in an org.<\/p>\n Iterable is created only when we have to create a complex scope or collection of records, Iterable is limited to 50000 records only.<\/p>\n The syntax of the start method is as below:<\/p>\n global (Database.QueryLocator | Iterable<sObject>) start(Database.BatchableContext \u00a0bc ) {}<\/p>\n After the collections of record is gathered the execute method is then next executed. This method is called for each batch, it takes a reference to database.BatchableContext object and a list of sObject. Batches are normally executed in the order they are received, but their execution order is not guaranteed.<\/p>\n The syntax of Execute method is as below:<\/p>\n global\u00a0void\u00a0execute(Database.BatchableContext\u00a0BC, list<P>){}<\/p>\n Once all the batches are executed, then the last method Finish is called. This method takes the batchable context as a parameter and is used to perform post processing task like sending an email.<\/p>\n Syntax of Finish method is as below:<\/p>\n global void finish(Database.BatchableContext BC){}<\/p>\n Each batch is considered as a separate transaction and they avail fresh set of apex governor limit, i.e. \u00a0if a batch of 500 records are being processed with scope of 50 then 10 batches are going to be executed separately and the governor limits will reset for each batch.<\/p>\n Examples of batch Classes<\/h2>\n global class UpdateAccountFields implements Database.Batchable<sObject>{<\/p>\n global final String Query;<\/p>\n global final String Entity;<\/p>\n global final String Field;<\/p>\n global final String Value;<\/p>\n global UpdateAccountFields(String q, String e, String f, String v){<\/p>\n Query=q; Entity=e; Field=f;Value=v;<\/p>\n }<\/p>\n global Database.QueryLocator start(Database.BatchableContext BC){<\/p>\n return Database.getQueryLocator(query);<\/p>\n }<\/p>\n global void execute(Database.BatchableContext BC,<\/p>\n List<sObject> scope){<\/p>\n for(Sobject s : scope){s.put(Field,Value);<\/p>\n }\u00a0\u00a0\u00a0\u00a0\u00a0 update scope;<\/p>\n }<\/p>\n global void finish(Database.BatchableContext BC){<\/p>\n }<\/p>\n }<\/p>\n To call this batch class we need to us the following code:<\/p>\n String q = ‘SELECT Industry FROM Account LIMIT 10’;<\/p>\n String e = ‘Account’;<\/p>\n String f = ‘Industry’;<\/p>\n String v = ‘Consulting’;<\/p>\n Id batchInstanceId = Database.executeBatch(new UpdateAccountFields(q,e,f,v), 5);<\/p>\n The following code is to re assign the account owner to a new one.<\/p>\n global class OwnerReassignment implements Database.Batchable<sObject>{<\/p>\n String query;<\/p>\n String email;<\/p>\n Id toUserId;<\/p>\n Id fromUserId;<\/p>\n global Database.querylocator start(Database.BatchableContext BC){<\/p>\n return Database.getQueryLocator(query);}<\/p>\n global void execute(Database.BatchableContext BC, List<sObject> scope){<\/p>\n List<Account> accns = new List<Account>();<\/p>\n for(sObject s : scope){Account a = (Account)s;<\/p>\n if(a.OwnerId==fromUserId){<\/p>\n a.OwnerId=toUserId;<\/p>\n accns.add(a);<\/p>\n }<\/p>\n }<\/p>\n update accns;<\/p>\n }<\/p>\n global void finish(Database.BatchableContext BC){<\/p>\n Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage();<\/p>\n mail.setToAddresses(new String[] {email});<\/p>\n mail.setReplyTo(‘batch@acme.com’);<\/p>\n mail.setSenderDisplayName(‘Batch Processing’);<\/p>\n mail.setSubject(‘Batch Process Completed’);<\/p>\n mail.setPlainTextBody(‘Batch Process has completed’);<\/p>\n Messaging.sendEmail(new Messaging.SingleEmailMessage[] { mail });<\/p>\n }<\/p>\n }<\/p>\n To call the owners reassign batch class we need to use the following code:<\/p>\n OwnerReassignment A = new OwnerReassignment();<\/p>\n A.query = ‘SELECT Id, Name, Ownerid FROM Account ‘ +<\/p>\n ‘WHERE ownerid=\\” + u.id + ‘\\”;<\/p>\n A.email=\u2019test@acme.com’;<\/p>\n A.fromUserId = u;<\/p>\n A.toUserId = u2;<\/p>\n ID id = Database.executeBatch(A);<\/p>\n To Allow Callout in the batch class we need it to implement another interface i.e. \u00a0Database.AllowsCallouts<\/p>\n Each batch execution is a different transaction and one transaction is unaware about the status and progress of the other transaction. The entire batch executed are asynchronous process and do not have a state after they have finished executing. To maintain the state and pass a value from one batch to another we need to specify another interface while defining the class, i.e. Database.Stateful.<\/p>\n Below is the code to aggregate the total of amount of opportunity.<\/p>\n global class SummarizeAccountTotal implements<\/p>\n Database.Batchable<sObject>, Database.Stateful{<\/p>\n global final String Query;<\/p>\n global integer Summary;<\/p>\n global SummarizeAccountTotal(String q){Query=q;<\/p>\n Summary = 0;<\/p>\n }<\/p>\n global Database.QueryLocator start(Database.BatchableContext BC){<\/p>\n return Database.getQueryLocator(query);<\/p>\n }<\/p>\n global void execute(<\/p>\n Database.BatchableContext BC,<\/p>\n List<sObject> scope){<\/p>\n for(sObject s : scope){<\/p>\n Summary = Integer.valueOf(s.get(‘total__c’))+Summary;<\/p>\n }<\/p>\n }<\/p>\n global void finish(Database.BatchableContext BC){<\/p>\n }<\/p>\n }<\/p>\n Batch Apex governor Limits<\/h2>\n \n 5 batch jobs can run concurrently at a time in a given organization<\/li>\n Upto 100 jobs can be held in the Apex Flex queue.<\/li>\n Maximum number of batch that can be executed is 250000 per rolling 24 hour periods. This limit is shared among the all asynchronous process like Future, Queueable and schedulable.<\/li>\n Maximum of 50 mil records can be returned by Database.querylocator and if more records are returned then the job is terminated immediately.<\/li>\n Maximum limit of a batch size is 2000, if higher value is set then the records are chunked into size of 2000, in case of iterable there is no upper limit.<\/li>\n A batch can implement a maximum of 100 callout and the call can be from any method i.e. start, execute and finish<\/li>\n<\/ol>\n Batch Apex Best Practice<\/h2>\n \n Take extreme precaution when scheduling a batch from a Trigger, as it can breach platform limit very easily.<\/li>\n While testing only one batch of apex can be tested using test.starttest() and Test.StopTest methods().<\/li>\n Use Database.Stateful only if you want to share instance member variable value across the whole job, otherwise it will impact the efficiency of the overall job performance.<\/li>\n Future methods are not allowed in a batch class, it cannot execute a future method<\/li>\n Another Batch job can be called from the finish method of the Batch class, it is called chaining batch job.<\/li>\n<\/ol>\n Also check the interview questions based on Batch Class<\/p>\n Batch class : Salesforce Interview Question<\/a><\/h4>\n","protected":false},"excerpt":{"rendered":" Asynchronous Apex, The Savior from Salesforce Governor Limits Asynchronous Apex, we all know how sometimes Salesforce Governor Limit can haunt us at times. With the limited amount of resource available due to the multi tenant architecture, we have to restrict our self with the optimum usage of the resources. But what if we want to … Continue reading Asynchronous Apex, The Savior from Salesforce Governor Limits<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[84],"tags":[40,79,61,74,45,75,38,83,42,82,55,51,52],"class_list":["post-976","post","type-post","status-publish","format-standard","hentry","category-asynchronous-apex","tag-apex","tag-apex-trigger","tag-dml","tag-dynamic","tag-dynamic-soql","tag-dynamic-sosl","tag-salesforce","tag-salesforce-admin-interview-questions","tag-salesforce-apex","tag-salesforce-developer-interview-questions","tag-salesforce-interview-questions","tag-soql","tag-visualforce"],"_links":{"self":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/976","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/comments?post=976"}],"version-history":[{"count":4,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/976\/revisions"}],"predecessor-version":[{"id":2203,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/976\/revisions\/2203"}],"wp:attachment":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media?parent=976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/categories?post=976"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/tags?post=976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}