Wechat development series 9 – Create C4C Social Media Message and Service within Wechat app

* Wechat development series 1 – setup your development environment
* Wechat development series 2 – development Q&A service using nodejs
* Wechat development series 3 – Trigger C4C Account creation in Wechat app
* Wechat development series 4 – Send C4C Data change notification to Wechat app
* Wechat development series 5 – embedded your UI5 application to Wechat app
* Wechat development series 6 – Retrieve Wechat User info via oAuth2 and display it in UI5 application
* Wechat development series 7 – use Redis to store Wechat conversation history
* Wechat development series 8 – Map integration
* Wechat development series 9 – Create C4C Social Media Message and Service within Wechat app

* Implemented feature

* Implementation detail

* How to create individual customer, social media user profile, and bind both together
* How to create social media message once end user sends a text to Wechat subscription account

In the second blog of this series, Wechat development series 2 – development Q&A service using nodejs we have developed a kind of Q&A service in Wechat.

In this blog, let’s replace the Q&A service hosted by tuning API with another style: everytime the end user of your test subscription account has sent some message to it, then create a corresponding social media message in C4C system ( and a new service request will also be automatically created together with that social media message ).

Implemented feature

1. When the end user has subscribed the Wechat account by pressing “Subscribe(关注)” button: In C4C system an individual customer for this end user who has subscribed the Wechat test account will automatically be created, together with a new social media user profile created as well and bound to this individual customer. The end user will receive a notification about created customer ID and profile ID once creation finishes in C4C system. The created information could also be monitored in console: The created customer could be found in C4C system with a custom Channel type displayed as “Jerry’s Wechat Channel”. The created social media user profile bound to this customer could be found in tab “Social Profiles”: 2. As long as end user sends some new text to the Wechat subscription account, a new social media message will be created in C4C. The end user will receive a notification in Wechat about the created message ID, in my example it is 59160. The created social media message could be found in tab “Social Media Messages”: And a new ticket is also automatically created for this social media message. The creation of this ticket is a standard behavior of C4C, no custom development is necessary.

Implementation detail

The feature described so far is developed based on the existing project used in previous blogs. You must first create a custom channel for Wechat in Business Configuration: Write down this channel type code 905 for created Wechat channel: And create a concrete channel based on the 905 custom channel type created just now, write down this channel ID ZJERRYWC as well.

How to create individual customer, social media user profile, and bind both together

In my github repository for this Wechat development series, module createAccountInC4C.js is responsible for individual customer creation. Once finished, it will call another two modules highlighted below to create social media user profile and link the user profile with created individual customer. For social media user profile creation, the ID of previous created custom channel for Wechat, 905, is hard coded in module implementation createSocialMediaProfile.js. In createAccountInC4C.js, these three steps are clearly mentioned in the comment and implementation: And createAccount will be called for event handler of “subscribe” event:

How to create social media message once end user sends a text to Wechat subscription account

The message creation is implemented in module createSocialMediaActivity.js. In unittest folder there is a unit test written to demonstrate how to use this module:

* o0KlM1i2_4-zHRmDk-IWGRlA1Cjc: the wechat ID of user who has sent the text to the test Subscription account
* 1003: the ID of new social media message to be created
* 6066: social media user profile of current wechat user who has sent the text to the test Subscription account
* ZJERRYWC: the custom Wechat channel ID created previously in C4C system
* “Hello C4C Agent….”: the text of social media message to be created

Call this createSocialMessage module in the event handler when a new text is sent by Wechat end user. http://bit.ly/2mXbRAD #SAP #SAPCloud #AI

8 Tips on How to Build a Natural Backlink Profile

Building natural backlinks has always been a problem for most online marketers, yet it’s one strategy that guarantees a massive return on investment. If website owners have no idea about backlink profiles, it’s hard to attract visitors and turn their websites into cash cows.

Google is becoming more interested in the type of links you have and where they come from. They’re changing their algorithm daily and you need to keep up with things like these https://www.linksmanagement.com/how_to_get_ranked_top_10_on_google/. In order to build effective backlinks, it’s important you do the following:

1. Monitor Links

Monitor your existing links and if you realize one of them is broken, don’t waste time fixing it. In fact, fixing a broken link is more difficult than building a new one. Therefore, keep checking your links and if any of them is found broken, it should be replaced with a new one as soon as possible.

2. Hire a Formidable Link Building Company

Link building companies that promise a large number of links at a low price are all phony. In fact, it is a good indicator that the links are coming from a low-quality sources and they’ll destroy your backlink profile. Hire a company that charges more but guarantees you links will improve your profile.

3. Avoid Buying Links Directly

Google is on the look out and will not hesitate to punish website owners who take shortcuts. It’s therefore recommended you hire a company that specializes in link building rather than buying existing links, which will only attract a penalty and ruin your profile.

4. Do Your Research Before Exchanging Links

It is normal for companies to exchange links. However, when it becomes extremely obvious, Google will find out and punish everyone involved. Consequently, it’s important you reduce the rate in which you exchange links. Too many in a short amount of time will cause Google to take action.

5. Avoid Directories

In early 2010, directories were the main platforms helping new websites get noticed. However, things have changed and Google does not play by the same rules. So, unless it’s a specific niche, directories will only offer low-quality backlinks.

6. Don’t Overuse Your Anchor Text

This is one of the mistakes website owners make. When they realize a specific keyword has improved their rankings, they want to use it again and again. Google does not like seeing the same anchor text being abused. Consequently, they will punish people who do this by pulling down their rankings.

7. Sites to Backlink

Having talked about things that Google doesn’t like and which will make your website to get punished it is important that we talk about things that you should focus on and which will give your website the diversity it requires to attract attention.

8. Link Back to Quality Sites

Ensure you link back to quality sites. The trouble is how to tell whether or not the site is of high quality. In general, high-quality sites will exhibit the following characteristics:

• A high number of social media followers
• Relevant information
• Quality content
• High domain authority

In conclusion, we hope you will use this knowledge to improve your backlink profile and attract more visitors to your website. Just ensure you provide your readers with high-quality hyperlinks, and ensure the links you acquire point to relevant pages on your website. http://bit.ly/2mVDvhg #SAP #SAPCloud #AI

Procedure to Convert Multiprovider to Composite provider

Hi,

This is Srinivas Dayana, Working for Cognizant Technology Solutions. I have 10 years of experience in BW and ABAP. I am working on SAP HANA for the past 4 years. As part of the Project requirement, we are currently Simplify few Processes and even want to use the optimised BW objects like ADSO and Composite Provider which will ease the migration from BW 7.4 to BW 7.5.

Summary:

As part of the Project requirement we have build a new data model using the ADSO and Composite Providers and we came across the scenario where there are almost 100 workbooks which are created by Business and all the workbooks will be effected when we switch from old Model to New Data model and Business have to recreate all the workbooks again which will effect Business reporting. So we are using the below conversion tool to convert the Multiprovider to Composite Provider and then enhance the Composite provider with the newly created composite provider so that none of the Queries will be effected and there will not be any impact on the workbooks which will save  lot of time for the business users.

Key Outcomes:

* Easy conversion of Multiprovider to Composite Provider
* Pros of using the below conversion tools
* Points to remember while using the approach

Introduction: We have Business scenario to convert the old BW Multiproviders to Composite Provider, so that we can use some additional functionalities like Join and perform operations on top of the existing MPRO’s. Business has so many Queries and Workbooks that are created on the same and we don’t want to change the existing Reports and Workbooks as that may have impact on the Business reporting.

This Conversion method will ease the Process of converting the Multiproviders to Composite provider with out having impact on Queries and Workbook.

The Below is the step by step Procedure to convert multiprovider to composite Provider:

Step 1: Create a new multiprovider for testing purpose

Step 2: Select the required sources for the multiprovider

Step 3: Identify the Fields that are required and the source from which the data should be populated for the field

Step 4: Activate the Multiprovider

Step 5: Execute the program RSO_CONVERT_IPRO_TO_HCPR

Step 6: Select the Infoprovider which we want to convert to Composite Provider. In this case we will use the multiprovider, which we have created for the test purpose.

Step 7: In the above screenshot , provide the name of the composite provider

* If we want the infoprovider name and the composite provider name to be same then give the same name as the Infoprovider
* We can also give a new name depending on the requirement

*In this case we want to create the Composite provider with the same name, as none of the existing Queries or Workbooks will not get effected.

Step 8: We cannot execute the above Program without giving backup provider name

Step 9: Provide the Backup infoprovider name  and execute in Simulate mode to check whether the Infoprovider can be converted to Composite provider or not.

Step 10: if there are no errors then we can go ahead with the conversion of Multiprovider to  a Composite Provider

Step 11: Execute the Program providing all the required Inputs and use the setting “Convert Infoprovider and copy Queries”

Step 12: Select the required Queries that we want to backup.

Step 13: Select the Required fields for the Queries

Step 14: Provide the Backup Query name, we cannot give the Query name same as the Backup Query  name, in the below example the report 3 will give the error as we have given the same name

Step 15: Provide the proper backup Query name and Proceed

Step 16: Check if there are no errors and confirm

Step 17: Multiprovider is now converted to a Composite Provider

Step 18: Open Query Designer and check for the Target and we can see one set of actual Queries and another set of Backup Queries

Step 19: Test the report before and after the changes

*Output of Query on multiprovider

*Output of Query on Composite Provider

Note: If we collect all the changes in the same Transport then we need to import the changes twice and if everything works fine and if we want to delete the Backup Queries, collect the Queries in separate Transport and import them separately.

The conversion is successful and in case of issues and we need to restore back to the old MPRO , please execute step 20.

Step 20: If the Conversion has some issues and the reports are not working fine we have setting to restore the backup. Select the setting “Restore backup” so that we will be converting back to the Old MPRO.

Note: The setting should be same as the setting during conversion. We need to Provide the exact same setting that we have provided when we have initially converted the Multiprovider to Composite provider or else Restore will not work, so make sure we have backup of the settings. We always need to select the Overwrite Existing HCPR option while doing the restore backup option

Step 21: We can see the Composite provider is set back again to multiprovider

Benefits of this Approach

* Easy Conversion of Multiprovider to Composite provider
* None of the Queries will be effected due to the conversion from Multiprovider to Composite provider
* Use the additional functionalities of composite provider
* None of the workbooks created on the Queries will be effected, so there will not be much impact on the Business due to the conversion

Hope this post is useful and i will update further post on SAP BW and SAP HANA when i have some new learning. http://bit.ly/2DRe7RI #SAP #SAPCloud #AI

Overview of 2017 SAP Inside Track Locations @SAPInsideTrack using Lumira

First, I used Lumira 1.31.9 Desktop to screen scrape the SAP Inside Track wiki

I manually entered the region and country – here are the data fields:

Month
City
Country
Region
Count

Of course, using Country I had to create a Geographic Hierarchy on the country – I decided to skip the city as Lumira didn’t recognize cities such as “Ballerup”

You can see that Brazil, Germany, and Australia held the most SAP Inside Tracks in 2017

Here is another clearer version of the map:

Counts by region are shown below:

Europe has the most.  North America is the lowest as ASUG has 38 chapters spanning the United States and Canada – I would expect to have fewer SAP Inside Tracks in North America as a result.  This year I attended ASUG chapter meetings myself.  I participated virtually in SAP Inside Track Bangalore thanks to the efforts of Shilpa Krishnaswamy

Of course, to have fun (there’s no visualization benefit to this) is to show animation of SAP Inside Tracks by month:

Another geo-pie map – there’s no visualization benefit here either, but more for a learning experience:

Because I was using Lumira 1.31.9, I wanted to try the “save for migration” feature:

How would this file act in Lumira Discovery?  I encountered this message:

A hard stop error…

I had to change the maps to offline maps:

And more confirmation shown above

Not all the maps converted as I would have liked, so I started over.

Lower left is the animation, and what is new is the marker map in the lower right.

On another canvas it was easy to filter on locations/cities with more than 1 SAP Inside Track in 2017 – shown above.

Reading Stephanie Evergreen’s book on visualization, I know that the above doesn’t display the data adequately – perhaps that is for another post…still it interesting to see how Lumira reflects the data on the maps.

So what is your take on SAP Inside Tracks 2017? http://bit.ly/2DTyH3V #SAP #SAPCloud #AI