1 2 3 8 Previous Next

SAP BusinessObjects Mobile

120 Posts

What is Mobile Page Layout?

            The Mobile Page Layout has been implemented mainly for supporting all layout scenarios of Webi Reports, as per the Report Element arrangements, defined on BI Launch-Pad.  This layout model helps user to design the Webi Reports with minimal design work, and user does not need to strain to place the report element in exact pixels or to align the report elements with accurate coordinate details. 

In this approach, the report elements are arranged and resized for the improved space efficiency and aesthetics, which work best when the report is displayed on tablet or a mobile device. The report page is cut up in to multiple columns and as per the coordinates the report elements will be grouped on the specific column. The report elements of a particular column will share space according to the proportion of actual size of the Report elements.

            It is recommended to use Mobile Page Layout, rather than Card Layout, as the Mobile Page Layout covers all the layout scenarios of a Webi Document, such as pagination, space efficiency, report element spanning.

 

A Report Page cut up into multiple columns:-

            The number of columns, created on the page, will be equivalent to the maximum number of report elements, which are located horizontally, without horizontal overlap with other report elements. In the below specified diagrams, it is explained with some examples.


 

Arrangement in WebiNumber of ColumnsDetail
1Screen Shot 2014-11-15 at 19.28.45.pngScreen Shot 2014-11-15 at 19.28.52.pngIn this layout, at maximum there are three reports elements, placed horizontally. The report elements are 1, 2 and 3. The Report element 2 comes to 2nd Column, because right side of Report element 1 ends before the left side report element 2.
2Screen Shot 2014-11-15 at 19.28.58.pngScreen Shot 2014-11-15 at 19.29.13.pngIn this layout, at maximum there are around 5 report elements, placed horizontally. The report elements are 1, 2, 5, 6 and 7.
3Screen Shot 2014-11-15 at 19.29.21.pngScreen Shot 2014-11-15 at 19.29.25.pngIn this Layout, the report element 2 remain on the first column itself, as it is overlapped with report element 1, and will be rendered one below the other.


Following statement will be easy to perceive, with the understanding of above examples.

 

In technical terms, a report element (2) will be placed in to a new column (on the right side), when at least one of its left side report element’s (1, 4, 8) right side boundary ends before the report element’s (2) left side boundary.

 

 

Why do we have column-based layout in Mobile Page Layout Model?

            For aligning report elements boundary to a nearest vertical or horizontal line, the layout needs to follow either a column based rendering or a row based rendering.  The main reason for following column based rendering in this layout model is to have space efficiency under a Vertical Table which may grow or shrink vertically, based on the number of rows, when filters are applied.

 

Pagination of Mobile Page Layout:-

            The Pagination of a Webi Report in mobile device will be done as per the Page Format setup of the report, defined in BI Launch Pad.  The default Webi Page Format is A4 size with Portrait orientation. When the page format is configured for other page size and orientation, the pagination with respective size is done in the mobile device screen as well.

 

Page FormatOn BI Launch PadOn Mobile Device
A4_Portrait on BILaunchpadScreen Shot 2014-11-15 at 19.39.11.pngScreen Shot 2014-11-15 at 19.40.08.png
A4_Landscape on BILaunchpadScreen Shot 2014-11-15 at 19.40.24.pngScreen Shot 2014-11-15 at 19.40.28.png

 

 

As shown in the snapshot, the arrangements of A4-Portrait of Webi Page in BI Launchpad will be same for both Portrait and Landscape orientation of Mobile WebI Page, i.e. when the orientation of mobile device screen is changed, the report elements will be just stretched to different dimension, and will not be moved to other page.

 

A Report element will not be spread across multiple pages:-

              In BI Launchpad, a Report element can be bigger than a Page size, hence it will spread across multiple page as show in the following snapshot.

Screen Shot 2014-11-15 at 19.40.49.png

But when the same report is rendered on Mobile Device screen, the Report elements will not be split or spread across multiple Pages. Instead a report element will be clipped with the page, where its origin resides. For instance, in the above example, the Pie Chart is spread on Page1 and Page2. But in the Mobile Device, the Pie chart will be displayed on Page1. And the vertical table in BI Launchpad is originated on Page1 and spread on Page2, Page3 and Page4. In the Mobile Device the table will be clipped and displayed inside Page1. Hence the report will be displayed in Mobile Device as per the below specified snapshot.


Screen Shot 2014-11-15 at 19.41.03.png

This webi report in Mobile Device has single page (only Page1) and the other pages (Page2, Page3, Page4) are not listed, as there is no report element, with its origin, on those pages.

 

Dimension of a Report element on Mobile Device:-

            Along with the space optimization on Mobile Device, Mobile Page Layout decides dimension of each Report element, based on the size proportion of a Report element against the size of a Report elements available on the particular page. For instance, the below Webi Report Page has Report elements with various different dimension and unaligned origins.

              When the same Report Page is rendered on Mobile Device, Based on the origin and dimension, each Report element will be aligned into a column, and the report element will be rendered one below the other inside the column.


Screen Shot 2014-11-15 at 19.41.21.png


The above Report Page will be displayed in Mobile device as per below snapshot. There are 2 columns, one column covers RP1 and RP2. And the other column covers RP3, RP4 and RP5. Here each column will get width based on the proportion of that column with all other columns.

Column width:-

On the first column, there are Report elements with maximum width as 2 inches (Width of RP1 or RP2). On the second column there are Report elements with maximum width as 3 inches (width of RP3). Here the width proportion of the columns is 2”:3”. When it is rendered on Mobile Device which has around 750 pixel width, as per the proportion, the first column will get 300px and the 2nd column will get 450px.

 

 

Report element height:-

              On the first column, there are 2 Report elements, one of which(RP1) has 3 inch height and other Report element(RP2) has 1 inch height. Here the height proportion is 3”:1”. When these report elements rendered on Mobile device, as per the proportion, RP1 will get 675px height and RP2 will get 225px height.


Screen Shot 2014-11-15 at 19.41.33.png


     On the Second Column, there are Report elements (RP3, RP4, RP5) with equal height of 2 inches. Here the height proportion of the report elements is 2”:2”:2”. Hence on the mobile device, each Report elements on the Column2 are rendered with equal height of 300px.

Report elements of a Column will have equal width:-

            The report elements of a particular column will have same width, which will be equal to the width of the column.

Space between Report elements:-

            Each Report elements and columns are rendered with 10px gap, on all of the sides. Even when there is more gap or no gap between report elements on BI Launchpad, there will be always a constant 10 px gap between report elements, when it is rendered on Mobile Device.

 

 

Report elements can be spanned across multiple columns:-

            A report element can be designed for spanning across multiple columns. For instance in the following Webi report page, the Line Chart is spread on both Column 1 and Column2.

Screen Shot 2014-11-15 at 19.41.52.png

The above webi report page will be rendered on Mobile Device as per the snapshot given below.

Screen Shot 2014-11-15 at 19.42.01.png

Tables on Mobile Page Layout :

            Tables on webi report may grow and shrink vertically, based on the applied filter values.  On the mobile device, whenever a Table shrinks on its height, the Report element, which resides under the table will occupy the space. If the below report element is another table and it is not spanned across multiple columns, then it will be moved up to occupy the space created by the shrunken table.

            When a Table grows on its height, it can grow up to the allotted height, which is derived from the proportion with other report elements on the same column.

  When the table content needs more height than the allotted size, then the Table will be vertically scrollable, within the allotted height. And when there is more number of columns, which could not be accommodated on the given width (column’s width), then the table will be horizontally scrollable, within the allotted height.


 

On BI LaunchpadOn Mobile Device
Screen Shot 2014-11-15 at 19.42.16.pngScreen Shot 2014-11-15 at 19.42.21.png

Based on the filter the Table has shrunk

and have just 4 rows

Screen Shot 2014-11-15 at 19.42.29.png

Table has shrunk,

and the gap is filled with Bar chart


Screen Shot 2014-11-15 at 19.42.34.png


Horizontal Alignment of report elements across columns: -

            The horizontal alignment of report elements across columns is achieved by keeping size proportion of the report elements equally on those columns. For instance, the following Webi Report page has 3 columns, and on each column report element height proportion is equal across the column.

            On the first column, the report element size proportion is 1.5”:2”:3”, likewise on the 2nd column also the size proportion as  1.5”:2”:3”. So RP2 and RP5 are horizontally aligned, as RP1 and RP4 heights on Mobile device are equal. And RP3 and RP6 are horizontally aligned, as RP1 + RP2 and RP4 + RP5 heights on Mobile device are equal.

            On the third column, the report element size proportion is 3.5”:3”. Based on this proportion, the sum of height of RP4 and RP5 will be equal to height of RP7. So RP8 will be horizontally aligned with RP3 and RP6.

              As the horizontal alignment of report elements are decided based on the height proportion, it is not necessary to keep the report elements exactly aligned origin on BI Launchpad.

Screen Shot 2014-11-15 at 19.42.44.png


Hence the above webi report will be rendered on Mobile device as per the below snapshot. Horizontal Alignment could not be achieved or will not consistent for the report elements, which comes below a Table, because when the table shrinks the report will be moved up automatically for space optimization, so alignment with other column report element will be disturbed. So it is suggested to use Charts or spanned Table, above the report elements, which need to be aligned horizontally.


Screen Shot 2014-11-15 at 19.43.10.png

Horizontal Alignment when there are Tables in the WebI Report:-

     When a table comes above to another Report element, due to the variable height of the table according to the number of rows, the other report element will keep on moving up and down. In such scenario, horizontal alignment across multiple columns can not maintained consistently.

Screen Shot 2014-11-15 at 21.50.34.png


In the above example report, the Pie Chart and the Line Chart is not horizontally aligned. In this scenario, we can follow following steps to arrange the report elements in horizontal alignment.

  • Make sure the table height is constant(for example, the number of rows of the table, or the content of the table should not be varied while applying different filter values)
  • Now the need is to slightly bring up the divider(between the bar chart and the line chart) in the second column.
  • This can be achieved either by reducing the bar chart height or by increasing the line chart height.
  • With some trials, we can achieve the horizontal alignment.


Sections on Mobile Page Layout:-

            When a Webi Report, which has sections, is displayed on Mobile Device, at a time a single section’s report elements only rendered. User can navigate to different section by selecting an item from the left side section navigation panel. For instance, the below webi report has 3 Charts are each section and it has one non-section report element(Vertical Table), above to the sections.


Screen Shot 2014-11-15 at 19.43.31.png


When the above webi report is opened on Mobile Device, initially the non-section report element will be displayed and no sections will be displayed. If there is no non-section report element, then initially the first section (2004) will be displayed. Then user can navigate to next section (2005), then the previous section will be cleared and the page will be rendered with the non-section report element (Vertical Table) and new section content (2005), as specified in the below snapshot.


Screen Shot 2014-11-15 at 19.43.45.png


Free cell on Mobile Page Layout: -

     Like other Report elements, Free cell follows all above-mentioned logics like size proportion, Spanning across columns and horizontal alignments. In addition to that the free cell can be used for creating empty space on the Mobile Device Report page, by keeping blank cell without any text.

One of the pain points observed when upgrading SAP BI Mobile SDK for iOS is migrating the preferences specified in DefaultSettings.plist file.This article provides a sample script to migrate the preferences.

 

We will be looking at two different approaches to write shell scripts.

 

Approach 1: Writing a shell script to overwrite specific values of the plist.

 

Let's consider the customization of the following 3 features:

  1. feature.email.enabled.default
  2. feature.streamwork.enabled.default
  3. feature.predefinedconnections.list.default:0

 

Sample script:

 

MOBI_BASE_PLIST="./DefaultSettings_v5.0.plist"

MOBI_MODIFIED_PLIST="./DefaultSettings_v4.4.plist"

MOBI_NEW_PLIST="./DefaultSettings_v5.0.plist"



declare -a cust_arr=( \

"Customizations:feature.email.enabled.default" \

"Customizations:feature.streamwork.enabled.default" \

"Customizations:feature.addconnection.SUP.enabled.default" \

"Customizations:feature.predefinedconnections.list.default:0" \

)

echo "The script uses files in following locations, please exit and change the paths in script if needed: "

echo "Base version of file: [${MOBI_BASE_PLIST}]"

echo "Customized version of file: [${MOBI_MODIFIED_PLIST}]"

echo ""

echo "##################################################################"

echo ""

read -p "Do you want to proceed? " -n 1 -r

echo

if [[ ! $REPLY =~ ^[Yy]$ ]]

then

exit 1

fi


# Loop through the items in the array.

for i in ${cust_arr[@]}

do

MOBI_MODIFIED_VAL=$(/usr/libexec/PlistBuddy -c "Print :$i" "${MOBI_MODIFIED_PLIST}")

if [ "$?" == "0" ] #Proceed only if entry exists in modified file

then

MOBI_ORIG_VAL=$(/usr/libexec/PlistBuddy -c "Print :$i" "${MOBI_BASE_PLIST}")

if [ "$?" == "0" ]

then

if [ "$MOBI_ORIG_VAL" != "$MOBI_MODIFIED_VAL" ]

then

echo Customization found: $i is changed from $MOBI_ORIG_VAL to $MOBI_MODIFIED_VAL.

/usr/libexec/PlistBuddy -c "Set :$i ${MOBI_MODIFIED_VAL}" "${MOBI_NEW_PLIST}"

fi

else

/usr/libexec/PlistBuddy -c "Add :$i string ${MOBI_MODIFIED_VAL}" "${MOBI_NEW_PLIST}"

fi

fi

done

if [ "$?" != "0" ]

then

  clear

  echo "##################################################################"

  echo "Script run is complete. No customizations were detected."

  echo ""

  echo "If you are sure that you had performed customizations, ensure that following information is correct, and you have sufficient read/write permissions: "

  echo ""

  echo "Base version of the file: [${MOBI_BASE_PLIST}]"

  echo "Customized version of the file: [${MOBI_MODIFIED_PLIST}]"

  echo "##################################################################"

fi

 

Approach 2: Writing a shell script that generates a shell script to overwrite specific values of the plist.

 

This script generates another script file(runGeneratedOverrides.sh in our example).

 

 

Let's consider the customization of the following 3 features:

  1. feature.email.enabled.default
  2. feature.streamwork.enabled.default
  3. feature.predefinedconnections.list.default:0

 

Sample script:

 

 

MOBI_BASE_PLIST="./DefaultSettings_v5.0.plist"

MOBI_MODIFIED_PLIST="./DefaultSettings_v4.4.plist"

MOBI_NEW_PLIST="./DefaultSettings_v5.0.plist"

MOBI_CHANGE_SCRIPT="./runGeneratedOverrides.sh"

 

 

declare -a cust_arr=( \

"Customizations:feature.email.enabled.default" \

"Customizations:feature.streamwork.enabled.default" \

"Customizations:feature.addconnection.SUP.enabled.default" \

"Customizations:feature.predefinedconnections.list.default:0" \

)

#Inform the user that they need to review the generate file for any discrepancies.

clear

echo "##################################################################"

echo "This script will generate the following file, deleting any existing copies: "

echo "  ${MOBI_CHANGE_SCRIPT}"

echo ""

echo "The script uses files in following locations, please exit and change path in the script if needed: "

echo "Base version of the file: [${MOBI_BASE_PLIST}]"

echo "Customized version of the file: [${MOBI_MODIFIED_PLIST}]"

echo ""

echo "You must review the generated file for its completeness  and make any additional changes that you desire."

echo "##################################################################"

echo ""

read -p "Do you want to proceed? " -n 1 -r

echo

if [[ ! $REPLY =~ ^[Yy]$ ]]

then

exit 1

fi

 

#copy the Modified plist file as Change plist file.

rm "${MOBI_CHANGE_SCRIPT}"

 

 

# Loop through the items in the array.

for i in ${cust_arr[@]}

do

MOBI_MODIFIED_VAL=$(/usr/libexec/PlistBuddy -c "Print :$i" "${MOBI_MODIFIED_PLIST}")

if [ "$?" == "0" ] #Proceed only if entry exists in modified file

then

MOBI_ORIG_VAL=$(/usr/libexec/PlistBuddy -c "Print :$i" "${MOBI_BASE_PLIST}")

if [ "$?" == "0" ]

then

if [ "$MOBI_ORIG_VAL" != "$MOBI_MODIFIED_VAL" ]

then

echo /usr/libexec/PlistBuddy -c \"Set :$i ${MOBI_MODIFIED_VAL}\" \"${MOBI_NEW_PLIST}\" >> "${MOBI_CHANGE_SCRIPT}"

fi

else

echo /usr/libexec/PlistBuddy -c \"Add :$i string ${MOBI_MODIFIED_VAL}\" \"${MOBI_NEW_PLIST}\" >> "${MOBI_CHANGE_SCRIPT}"

fi

fi

done

 

#Mark the script as an executable

chmod +x "${MOBI_CHANGE_SCRIPT}"

 

if [ "$?" == "0" ]

then

  clear

  echo "##################################################################"

  echo "Script run is complete. Please review the following file for its completeness and make any additional changes that you desire: "

  echo ""

  echo "  ${MOBI_CHANGE_SCRIPT}"

  echo ""

  echo "##################################################################"

  echo ""

else

  clear

  echo "##################################################################"

  echo "Script run is complete. No customizations were detected."

  echo ""

  echo "If you are sure that you had performed customizations, ensure that following information is correct, and you have sufficient read/write permissions: "

  echo ""

  echo "Base version of the file: [${MOBI_BASE_PLIST}]"

  echo "Customized version of file: [${MOBI_MODIFIED_PLIST}]"

  echo ""

  echo "Script output file: [${MOBI_CHANGE_SCRIPT}]"

  echo "##################################################################"

fi


Shell scripts implementing both the approaches are attached to this article as .txt files. Kindly rename them to .sh formats after downloading.


Prerequisite for this configuration:-

  • SAP BusinessObjects Platform Configured for SAP authentication.
  • Support for SSO is from SAP BusinessObjects 4.0 SP08 or SAP BusinessObjects 4.1 SP02 onwards.
  • Basic Authentication URL, Which takes in SAP Authentication details and generates the MYSAPSSO2 Cookie for SSO.
  • Support from SUP 2.2.4 onwards.


Configuring Mobile Server for SSO Via SAP Logon tickets MYSAPSSO2 Cookie based:-


Below are the settings that need to be done for making the Mobile Server Look for MYSAPSSO2 Cookie in client request


MobileBIService Configuration:-


sso.properties file in MobileBIService config folder

====================================================


# You can configure mobile server to connect multiple CMS, specify default CMS id here

default.cms.identifier=<id>

 

# You can specify IP Address/Qualified Name/Alias for your CMS here

<id>.aliases=FQN of Mobile Server, IP address

 

# You can specify the sap system details here

<id>.sap.sid=SAP system SID

<id>.sap.client=SAP system client ID

 

# [You can specify name of Cookie here, if its other than default (siteminder default is SMSESSION, sap logon ticket default is MYSAPSSO2)

<id>.cookie.name=MYSAPSSO2

 

# You can specify the Authentication type here.  secLDAP, secWinAD, secEnterprise, secSAPR3

<id>.authentication.type=secSAPR3

 

# Specify the default authentication scheme here. USERPASS, BASIC, BOETOKEN, COOKIE, TRUST

<id>.authentication.scheme=MYSAPSSO2

 

 

Authscheme.properties file in the MobileBIService config folder:-

=================================================


# default User/Password log-on implementation

USERPASS=com.businessobjects.mobilebi.server.logon.impl.UserPass

 

# allows you to configure WCAToken, Default Token or any other BOE Token

BOETOKEN=com.businessobjects.mobilebi.server.logon.impl.Token

 

# allows you to configure SAP SSO2 Cookie

MYSAPSSO2=com.businessobjects.mobilebi.server.logon.impl.MySapSSO2

 

Configuring SUP for Mobile SSO Via SAP Logon tickets MYSAPSSO2 Cookie based:-


  • Login to SCC

SCC.png

 

Steps to create Security Configuration:

  • Security -> New -> Enter name (here for Ex., MobiSec)

        Note:- Do make a note of this name as it will used in future steps and at the client.

  • Select the created Security Configuration from tab on left hand side
  • Go to Authentication Tab -> New ->Authentication Provider -> Select HttpAuthenticationLoginModule
  • Specify your BASIC authentication URL for Validation SAP UserName and Password

 

Note:- URL -> Basic Auth URL with SAP authentication should issue ticket with MYSAPSSO2 Cookie    


Example:-http://10.10.10.10:8080/MobileBIService/MessageHandlerServlet?message=GetVersion

Authentication Module.png

 

  • Specify SSO Cookie Name -> MYSAPSSO2


Cookie Parameter.png

  • Click to save the configuration.


  • Delete existing Provider Type(NoSecLoginModule)

 

     Delete Existing Provider.png

 

  • General Tab -> Validate and Apply

   

        Note:-This step has to pass before going ahead with any other configuration

 

     Validate Settings.png

 

Steps to create an Application and Application Template:

  • Applications -> New
  • Enter Application Id and name (Id = MobiApp). Make a note of the Id as it would be used by the client.
  • Select the Security configuration (here MobiSec).

Creating Application ID.png

 

  • On Next -> Proxy Tab -> Give value to Application Push Point -> http://<Mobile BI Server>/MobileBIService/MessageHandlerServlet

        Example:- http://10.10.10.10:8080/MobileBIService/MessageHandlerServlet

  • Creating proxy pool for Mobile Server


Creating Proxy Pool whitelisting URL.png


Configuring the Mobile Configuration Server for importing SSO connection


MobiServer Configuration:-


Server.properties file


Example Connection:-


SSOSUPSAP.DisplayName:SSO_SUP_SAP

SSOSUPSAP.BOBJ_MOBILE_CONNECTION_TYPE_STRING=SUP

SSOSUPSAP.BOBJ_MOBILE_SUP_APP_ID= MobiApp(your Mobile Application ID)

SSOSUPSAP.BOBJ_MOBILE_SUP_SECURITY_CONFIG_NAME= your Security configuration Name

SSOSUPSAP.BOBJ_MOBILE_SUP_SERVER=SUP server IP or FQN

SSOSUPSAP.BOBJ_MOBILE_SUP_PORT=5001(your SUP Message Server port)

SSOSUPSAP.BOBJ_MOBILE_SUP_FARM_ID=0(your SUP FARM ID)

SSOSUPSAP.BOBJ_MOBILE_SSO_ENABLED=true

SSOSUPSAP.BOBJ_MOBILE_SSO_TYPE=SSO2COOKIE


Import the connection and Connect from SAP BusinessObjects Mobile.

Hello Everyone,

 

 

 

There will be situations where we would like to hyperlink to a report from an email or pdf. In case if your users use both mobile app as well as browsers,

you need to make sure you put both these links in all your communications to make it easy for the user.

 

 

Here is a simple method to overcome the issue with a single URL for both mobile and laptop/desktop. When the user clicks on the link depending on the device the URL is accessed from he/she is redirected appropriately.

Developed the script in simple asp format(on IIS server of course), but with this logic you should be able to develop script in any language of your choice.

 

 


Replace the following with your server details.

 

<<YOUR_CONNECTIONNAME>>

<<YOUR_SERVER>>:<<YOUR_PORT>>

<<YOUR_CMS>>

 


Example URL with Parameters:

 

     http://<<YOUR_IIS_SERVER>>/redirect.asp?cuid=XXXXXXX&report_type=webi

     http://<<YOUR_IIS_SERVER>>/redirect.asp?cuid=YYYYYYY&report_type=album

 

 

Save the below code in an asp file and host is on an IIS server after replacing the text as mentioned above.

 

 

<%

Option Explicit

Dim user_agent, mobile_browser, Regex, match, mobile_agents, mobile_ua, i, size

Dim report_cuid

Dim report_type

Dim viewSetId

Dim url_mobile_redirect

Dim url_pc_redir

 

 

 

report_cuid = Request.QueryString("report_cuid")

report_type =Request.QueryString("report_type")

viewSetId =Request.QueryString("viewSetId")

 

 

user_agent = Request.ServerVariables("HTTP_USER_AGENT")

 

 

url_mobile_redirect ="sapbi://OpenDoc/?authType=secEnterprise&connection_name=<<YOUR_CONNECTIONNAME>>&server_url=http://<<YOUR_SERVER>>:<<YOUR_PORT>>&ConnectionType=BOEConnection&cms=<<YOUR_CMS>>&type="&report_type&"&iDocID="& URLDecode(report_cuid)

 

 

If report_type="album" Then

  url_pc_redir ="http://<<YOUR_SERVER>>:<<YOUR_PORT>>/explorer/index.jsp?application=portal&viewSetId="& viewSetId

  url_mobile_redirect=url_mobile_redirect&"&explorerID="& URLDecode(viewSetId)

ELSE

  url_pc_redir ="http://<<YOUR_SERVER>>:<<YOUR_PORT>>/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID="&report_cuid

END If

 

 

mobile_browser = 0

 

 

Set Regex = New RegExp

With Regex

   .Pattern = "(up.browser|up.link|mmp|symbian|smartphone|midp|wap|phone|windows ce|pda|mobile|mini|palm)"

   .IgnoreCase = True

   .Global = True

End With

 

match = Regex.Test(user_agent)

 

If match Then mobile_browser = mobile_browser+1

 

If InStr(Request.ServerVariables("HTTP_ACCEPT"), "application/vnd.wap.xhtml+xml") Or Not IsEmpty(Request.ServerVariables("HTTP_X_PROFILE")) Or Not IsEmpty(Request.ServerVariables("HTTP_PROFILE")) Then

   mobile_browser = mobile_browser+1

end If

 

mobile_agents = Array("w3c ", "acs-", "alav", "alca", "amoi", "audi", "avan", "benq", "bird", "blac", "blaz", "brew", "cell", "cldc", "cmd-", "dang", "doco", "eric", "hipt", "inno", "ipaq", "java", "jigs", "kddi", "keji", "leno", "lg-c", "lg-d", "lg-g", "lge-", "maui", "maxo", "midp", "mits", "mmef", "mobi", "mot-", "moto", "mwbp", "nec-", "newt", "noki", "oper", "palm", "pana", "pant", "phil", "play", "port", "prox", "qwap", "sage", "sams", "sany", "sch-", "sec-", "send", "seri", "sgh-", "shar", "sie-", "siem", "smal", "smar", "sony", "sph-", "symb", "t-mo", "teli", "tim-", "tosh", "tsm-", "upg1", "upsi", "vk-v", "voda", "wap-", "wapa", "wapi", "wapp", "wapr", "webc", "winw", "winw", "xda", "xda-")

size = Ubound(mobile_agents)

mobile_ua = LCase(Left(user_agent, 4))

 

For i=0 To size

   If mobile_agents(i) = mobile_ua Then

      mobile_browser = mobile_browser+1

      Exit For

   End If

Next

 

 

If mobile_browser>0 Then

    'This means that the link was accessed from a mobile device

            Response.redirect(url_mobile_redirect )

Else

   'This means that the link was accessed from laptop/desktop

            Response.redirect(url_pc_redir)

End If

 


Function URLDecode(sConvert)

          Dim aSplit

          Dim sOutput

          Dim I

              If IsNull(sConvert) Then

                      URLDecode = ""

                      Exit Function

              End If

 

    ' convert all pluses to spaces

         sOutput = REPLACE(sConvert, "+", " ")

 

    ' next convert %hexdigits to the character

         aSplit = Split(sOutput, "%")

 

         If IsArray(aSplit) Then

                sOutput = aSplit(0)

                For I = 0 to UBound(aSplit) - 1

                  sOutput = sOutput & _

                    Chr("&H" & Left(aSplit(i + 1), 2)) &_

                         Right(aSplit(i + 1), Len(aSplit(i + 1)) - 2)

                Next

         End If

    URLDecode = sOutput

End Function

 

%>

 

 

~Naras~

SAP Business Objects Mobile 6.1.6 App for IOS got released 3rd November 2014.

 

 

Mobi now aligns with Flat UI design & supports IOS 8

01.JPG

 

Mobi now supports hierarchical display of categories

(disabled by default, enabled with “feature.home.category.nested.enabled=true” in client settings)

 

02.JPG

 

User can double tap on a report part to zoom in and zoom out

 

03.JPG

 

Notifications

 

Mobi App Icon now has a badge to show new notifications. New Notification Panel allows user to view all notifications in one place.

 

04.JPG

 

User can also tap on available notifications to view target documents. Now you have one “Auto update” for both BI Inbox and Documents. It can be disabled, enabled only for WIFI or enabled for both WIFI and cellular data. Newly added documents are also available as notifications in notification panel. Mobi application does not require a user action to get notifications & BI inbox content. It automatically gets them for an active connection.

 

05.JPG

 

06.JPG

Hyperlink Content in “work offline” Mode

  • Downloaded hyperlink content can now be accessed in “work offline” mode. This option is enabled with “feature.hyperlink.offline.enabled=true”.
  • This may require internet access based on the URL used in hyperlink.
  • Hyperlinks can now be created to access local html pages bundled with application built using Mobile BI SDK

 

 

Explorer Content Listing on Mobile BI

  • Currently all explorer content is listed on mobile devices, irrespective of being assigned to mobile category or not (category assignment possible for explorer artifacts since BI 4.1)
  • A new property is being introduced in mobi.properties to change this behavior. “default.listing.explorer.category.only=true” will force explorer documents to list only when they are assigned to mobile category
  • This property has a mobile server dependency

    07.jpg

 

Dashboards Listing on Mobile BI

  • Currently Dashboard content is listed on mobile device if any of the following is true
    • If it is assigned to mobile category
    • If it is enabled for mobile while saving
  • A new property is being introduced in mobi.properties to change this behavior. “default.listing.xcelsius.category.only=true” will force Dashboard documents to list only when they are assigned to mobile category (it should be noted this property only influence listing and in order for dashboard documents to be correctly displayed on mobile, they should be saved for mobile from dashboard designer)
  • This property has a mobile server dependency

    07.jpg


Dashboards Performance Improvements

  • Targeted performance improvements to reduce the initialization and loading time for dashboards (Has dependency on BI 4.1 SP05)
  • An option to enable “Prefer Cache” for downloaded dashboards. When it is set to true, application loads the dashboard content from cache even if the live connection is available. This option is available with client settings property “feature.dashboards.prefer.cache.enabled=true”

08.JPG

 

Option to clear HTTP Cache

  • An option is now provided to clear Http Cache.
  • Navigate to the option as follows:   Application Settings    >    Additional Settings    >   Clear Data   >  Remove Application Cache Data

09.JPG

 

Enhancement to SSO support

  • Support for more than one entitlement systems (SAP R3) for SSO using MYSAPSSO2 Cookie
  • Support for providing identity using X509 certificates when deployment involves reverse proxy or SUP/SMP or any such case where certificate reaches mobile server as “SSL_CLIENT_CERT” header
  • SSO enhancements have dependency on Mobile Server

        10.jpg

 

Enhanced Support for Report Element Linking (REL)

  • Support of REL (all objects) for all report parts
  • Support of REL (single object) on stacked bar chart. With this addition, now REL (single object) works for all report parts
  • Support of REL on tables with breaks

 


Enhanced Support for Open Document Link

  • Support opening up a Open Doc link in Lumira Story
  • Support for "sReportPart" and “mode" in Open Document Links
  • Support for navigation to report part within section in open document link (hierarchical sections are not yet supported)

 

 

Hyperlink & Report Element Link Color

Hyperlink and Report Element Link color on Mobi can now be customized by report designer

 

11.JPG

 

Enhanced Support for Input Controls

  • Support for Input controls defined on Variables that have Custom Lov defined
  • This feature has dependency on BOE 4.1 SP05 release of Mobile Server

11.5.JPG

 

11.8.JPG

 

Client Settings (Available since SAP Mobile BI 6.1 IOS)

 

feature.home.category.nested.enabledThis property allows the administrator to enable hierarchical display of categories on Mobile BI application. Its default value is "false".
feature.hyperlink.offline.enabledDownloaded hyperlink content can now be accessed in “work offline” mode. This can be enabled by setting the mentioned property to true.
feature.dashboards.prefer.cache.enabledThis property enables an option of "Prefer Cache" for downloaded Dashboards. [enabling Prefer Cache application loads the dashboard content from cache even if the live connection is available]
feature.notification.polling.intervalThis property allows an administrator to configure the time interval between two requests for checking available notifications.
feature.autoupdate.enabledThis property can be used by administrator to disable auto update feature for documents/instances. Auto update is enabled by default.
feature.autoupdate.bi.inbox.enabledThis property allows an administrator to disable the auto-download of BI Inbox documents only. Auto update  for BI Inbox content is enabled by default.

 

The SAP Help has been updated yet but when it is it will be at SAP BusinessObjects Mobile for iOS – SAP Help Portal Page

SAP Mobile BI App is available for Apple, Android & Blackberry devices. Content support across platforms and devices with different form factors is as follows

 

iPAD         iPhone        

Android Tablet

Android Phone
WebiYesYesYesYes
Webi As PdfYesYesNoNo
CrystalYesYesNoNo
Crystal As PdfYesYesNoNo
HyperlinkYesYesYesYes
DashboardsYesNoYesNo
Design StudioYesYesYesYes
ExplorerYesYesNoNo
LumiraYesNoNoNo

 

Note: As on today SAP Mobile BI App is not available on windows 8 tablet or phones.

 

 

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

Listing of an artifact on SAP Mobile BI Application is controlled by multiple factors. Following factors influence all content types

  • Whether the content type is supported on that device platform (i.e. IOS, Android, Blackberry etc.)
  • Whether the logged in user has access to that content type (this is restricted by disallowing rights on certain folders)


Then there are content type specific factor which determines whether it will be listed or not

  • Web Intelligence (Webi) - Webi artifacts are listed only when they are assigned to mobile category
  • Crystal (CrystalReport) - Crystal artifacts are listed only when they are assigned to mobile category
  • Explorer (DataDiscovery, DataDiscoveryAlbum) - All explorer artifacts that user is allowed to access are listed in Mobile App
  • Hyperlink (Hyperlink) - Hyperlink artifacts are listed only when they are assigned to mobile category.
  • Dashboards (XL.XcelsiusEnterprise) - Dashboards are listed when they are saved for mobile from Dashboard Designer
  • Design Studio (AAD.AnalysisAplication) - Design Studio artifacts are listed only when they are assigned to mobile category


This will help an administrator/user to determine why a particular artifact is listed/not listed.

 

Update: Listing behavior can be influenced for Explorer and Dashboard content. For more information refer "Explorer Content Listing on Mobile BI" & "Dashboards Listing on Mobile BI" sections in What is new in SAP BusinessObjects Mobile 6.1 (iOS)

The compatible MOBI app version with iOS8 will be V 6.0.9. We have already uploaded the new patch (v 6.0.9) to AppStore and should be available for download soon.

 

If you have upgraded your device to iOS8, you might face few UI issues and abnormal exit of application on some specific workflows. We have fixed these issues in the next patch version 6.0.9

 

If you are using older version of MOBI app  (like version 5.x or even 6.0.8)  built using SDK, we recommend you to download the latest SDK package (version 6.0.9) from Service Market Place (SMP) and rebuild the app before moving to iOS8. SDK package will be available for download from SMP once app is live in iTunes.Please continue to use XCode 5.x to build the application. Compilation using XCode 6.x is not yet supported and application may exhibit user interface issues.

 

Feel free to reach out to me if you have further questions

 

Regards

Srikanth

A user can directly import connections from Configuration Server (MOBIServer). In order for end user to be able to do that, mobile server administrator need to add the connections and their details in server.properties.


The list of parameters that can be used while defining connection in MOBI Server are as follows


Parameterin server.propertiesBasicSSOSUPSMPPossible Values
Name of connectionDisplayNameY
Type of connectionBOBJ_MOBILE_CONNECTION_TYPE_STRINGYBOESUPConnection, BOESMPConnection,
BOEConnection etc.
CMS Name or ClusterBOBJ_MOBILE_CMSY
Mobile Server or SUP/SMP Server URLBOBJ_MOBILE_URL (incase of Mobile Server)
BOBJ_MOBILE_SUP_SERVER (incase of SUP Server)
Y
AuthenticationTypeBOBJ_MOBILE_AUTH_METHODYsecEnterprise, secLDAP, secSAPR3, secWINAD
Is it a SSO connection?BOBJ_MOBILE_SSO_ENABLEDYtrue, false
Type of SSO Configured?BOBJ_MOBILE_SSO_TYPEYX509Certificate, SSO2COOKIE, SITEMINDER_BASIC,
TRUSTED_AUTH_Basic, TRUSTED_AUTH_FORM, SSO_Form, SSO2COOKIE_QueryString
If X509 Certificates used, then how are they configured?BOBJ_MOBILE_CERTIFICATE_REQUIRED_FOR_NETWORKYCertificateMandatory, CertificateOptional
URL that will provide SSO2COOKIEBOBJ_MOBILE_SSO_QUERY_URLY
Form that will generate SSO2COOKIEBOBJ_MOBILE_SSO_FORM_URLY
SSO Cookie Name if different than standardBOBJ_MOBILE_SSO_COOKIE_NAMEY
SAP R3 system in case of SSOBOBJ_MOBILE_SSO_SAP_SYSTEMYABC^200, XYZ^100 etc.
SUP Farm IDBOBJ_MOBILE_SUP_FARM_IDY
SUP/SMP Security Configuration NameBOBJ_MOBILE_SUP_SECURITY_CONFIG_NAMEYY
SUP PortBOBJ_MOBILE_SUP_PORTY
SUP/SMP Application IDBOBJ_MOBILE_SUP_APP_IDYY
SMP Proxy Connection NameBOBJ_MOBILE_SUP_PROXY_CONNY


As an administrator if you would like to create connections using SAP BI Links, you would like to have a ready list of parameters that are available to you for defining the connection correctly.

 

Parameter Description in SAP BI URLBasicSSOSUPSMPPossible Values
Name of connectionconnection_nameY
Type of connectionConnectionTypeYBOESUPConnection, BOESMPConnection,
BOEConnection etc.
CMS Name or ClustercmsY
Mobile Server or SUP/SMP Server URLserver_urlY
AuthenticationTypeauthTypeYsecEnterprise, secLDAP, secSAPR3, secWINAD
Is it a SSO connection?isSSOYYES,NO (in SAP BI Link)
Type of SSO Configured?SSOTypeYX509Certificate, SSO2COOKIE, SITEMINDER_BASIC,
TRUSTED_AUTH_Basic, TRUSTED_AUTH_FORM, SSO_Form, SSO2COOKIE_QueryString
If X509 Certificates used, then how are they configured?isCertificateRequiredYCertificateMandatory, CertificateOptional
URL that will provide SSO2COOKIEsso2CookieQueryURLY
Form that will generate SSO2COOKIEssoFormURLY
SSO Cookie Name if different than standardssoCookieNameY
SAP R3 system in case of SSOsapsysYABC^200, XYZ^100 etc.
SUP Farm IDSUP_Farm_IDY
SUP/SMP Security Configuration NameSec_ConfigYY
SUP PortSUP_PortY
SUP/SMP Application IDApplication_IDYY
SMP Proxy Connection NameproxyConnectionY

 

 

BOE connection


Add a connectionsapbi://addconnection?ConnectionType=BOEConnection&name=ConnectionName&server_url=ServerName/IP:Port&cms=101.01.01.01:Port&authType=AuthenticationType&default=yes/no
Delete a connection

sapbi://DeleteConnection?

ConnectionType=BOEConnection&name=Tom&server_url=10.53.10.10:8080&cms=10.53.10.10&authType=secEnterprise&default=no

Modify a connection

sapbi://ModifyConnection?ConnectionType=BOEConnection&ConnectionName_Prev=Conn1&ConnectionName_New=Conn2&Server_Url_Prev=10.53.10.10:8080&Server_Url_New=10.10.10.10

:1010&CMS_Prev=10.53.10.10&CMS_New=10.10.10.10&AuthType_Prev=secEnterprise&AuthType_New=secLDAP&default=yes&UserName_Prev=Administrator


SUP connection


Add a connection

sapbi://addconnection?ConnectionType=SUPConnection&Application_ID=MobiApp&Sec_Config=MobiSec&server_url=10.53.129.243&SUP _Port=5001&SUP_Farm_ID=0

Delete a connection

sapbi://DeleteConnection?ConnectionType=SUPConnection

Modify a connection

sapbi://ModifyConnection?ConnectionType=SUPConnection&Application_ID=MobiApp1&Sec_Config=MobiSec1&server_url=10.10.10.10&SUP_Port=5001&SUP_Farm_ID=0


Note: While modifying a connection normally you have to repeat each parameter twice - one with "Prev" and another with "New" suffix. However, in case of SUP connection that is not required. This is because you can have only one SUP connection.

SAP Mobile BI does not allow SSO connections to be created manually.

 

Following are the options for SSO connections


  • You can directly import these connections from the Configuration Server (MOBIServer)
    • Administrator can configure these connections at following location
      • Copy the server.properties from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
      • Then modify the server.properties file in custom folder
    • Choose your new connection identifier, say we choose 'mysso'. Add that to mobi.connections
    • Provide the connection properties and save the server.properties file
    • Now deploy the MOBIServer again after changes mentioned above.Once done, you can execute the following URL to check if the properties are configured correctly or not. [http://<server>:<port>/MOBIServer/MobiConfigurationServlet?RequestType=ServerList ]             

 

       

  • You can use MDM tools to publish connections if devices are IOS7 and above
    • For devices with iOS 7 or higher, Apple provides the "Managed App Configuration" functionality. This functionality allows a Mobile Device Management (MDM) server to push down a configuration dictionary into the managed app's NSUserDefaults for the purpose of remotely configuring settings
    • You can configure a single predefined connection or multiple predefined connections in the application by specifying values for the conn.list.(n) property on the MDM server, where 'n' is the array index starting with a value of 1. Each array item is of the type "String" and the value of each item corresponds to a connection URL.
    • For example, you can specify a predefined connection URL for a BOE server connection with the syntax shown below

               conn.list.1=<specify the sap bi link for SSO connection here>


  • You can use SDK to generate build that already has connection created.


Useful Links


PS: Once you have created SSO connection on your device, you can always share that connection with other users. Choose that connection, click share and that will generate the link for you

Hello Mobi Users,

 

With the iOS 8 set to release this fall, we would like to understand which iOS version you are using today and what plans you may have to upgrade to iOS 8, once it becomes available. Today, App Store distribution by OS  shows us that 90% of iOS devices is already using iOS 7 ( link)

 

So that we can better plan for iOS 8 support, please respond to this short, 2-question survey (link below).

 

If you have additional questions/inputs, you can also reach me via this blog or email

 

Survey link: https://www.sapsurvey.com/cgi-bin/qwebcorporate.dll?idx=CVV5AX

 

Note: This survey ends by 8th August

 

Regards

Srikanth

http://scn.sap.com/servlet/JiveServlet/showImage/38-110215-491572/asugdcodeimage.png

 

Continuing with the Meet the Speaker ASUG SAP d-code speaker series I am pleased to introduce Peter Chen of Deloitte

 

He is presenting on session EA114 Practical Lessons from Deloitte Global's Successful Mobile BI Launch

 

From the abstract:

 

Deloitte Global began their mobile BI journey in late 2012, from prototyping, SAP BusinessObjects Business Intelligence 4.0 upgrade, mobile dashboard development, security evaluation and LDAP authentication, mobile app customization and deployment, to a successful launch. Practical lessons were learned along the way and are ready to be shared.

Peter PIC.png


About Peter (from the abstract) (pictured to the right, photo provided by Peter)

Peter has been working with SAP ERP/BW/BI/BPC since 1998, and has played progressive roles in SAP implementations. Currently Peter is responsible for the Deloitte Global Finance Reporting, which included the CFO dashboarding and Mobile BI roll-out

 

Questions:

 

What is your role at Deloitte?

I have been the Deloitte Global Finance Reporting manager, and the Enterprise BI architect prior to that. I am responsible for designing and delivering  analytical solutions; managing the BI best practices and roadmaps; supporting the DTTL BPC planning and forecasting processes; and implementing  BI projects---which include the Global Finance Mobile BI and Central Finance Mobile BI initiatives.

 

What is your professional background?

I started my career in EDS(HP)and I have been a SAP project leader and BW/BI/BPC Solution Architect with over 15 years of progressive experience in global SAP ERP/BW/BI support and implementations.   I am a member of the ASUG Mobile BI influence Council (see Power of ASUG Influence : How ASUG members Influenced SAP BusinessObjects Mobile BI Solution and Learn how ASUG Members Influenced BusinessObjects Mobile BI Solution

 

 

I have participated in the partners testing for SAP Design Studio, Lumira and Mobile BI.  See his blog The warehousing benefit of the SAP business warehouse......

 

After completing the B.Sc degree in Beijing University, I came to the United States for graduate study. Briefly studied in Georgia Tech, before completing the Ph.D. in biomedical research from Northwestern University, a post-doc program at University of Chicago, and Computer Career Program at DePaul University.

 

 

What are some fun facts about Peter?

 

I am a loyal 49ers fan who recently visited the 49ers’ brand new stadium in Santa Clara.

On the subject of superstition in sports:  My arrival had apparently brought good lucks to his favorite teams:

1) Studied in Georgia Tech in 1990 – coincided with the Yellow Jackets’ only final 4 appearance and football National championship.

2) I arrived in Chicago in 91, when the Chicago Bulls started their historic 6-peat.

3) I visited SF the first time in 94, when the 49ners overcame the Cowboys that had beaten them the previous 2 years.

I am looking forward to his ASUG Mobile BI session at SAP d-code Las Vegas.  For a complete list of ASUG sessions, click this link.

 

 

You can follow Peter on twitter at @ccpg04

 

Join ASUG and other community members at SAP d-code Las Vegas

 

SAP d-code 2014 LAS VEGAS
OCTOBER 20-24
Venetian/Palazzo Congress Center


Save the date Monday, October 20th for ASUG SAP d-code Pre-conference Day


Related:

ASUG SAP d-code SAP BW 7.4 powered by SAP HANA Speaker - Introducing Pawel Mierski

ASUG SAP d-code Sessions Are Published - Featuring SAP Mentors

SAP's Srikanth R Rao K provided this webcast.  Documentation is also now live here – http://help.sap.com/boall_en

 

Mobile BI 6.0.3 for iOS is available today from iTunes.  The Android version will be available in a week (planned)

 

1favorites.png

Figure 1: Source: SAP

 

Figure shows Favorites as an actionable icon

2defaultfavorites.png

Figure 2: Source: SAP

 

If documents are marked as favorites, favorites will default

3doclinks.png

Figure 3: Source: SAP

 

Documents requiring an online connection have distinct thumbnail

4wifi.png

Figure 4: Source: SAP

 

Automatic updates of documents when connected to WiFi

5offline.png

Figure 5: Source: SAP

 

Work offline button is available as shown in Figure 5.

6smp.png

Figure 6: Source: SAP

 

SAP Mobile Platform 3.0 is and Cloud is supported by MobI (except Dashboards is not supported on SMP Cloud)

7mdm.png

Figure 7: Source: SAP

 

Figure 7 covers configuration support for iOS7 devices

8webi.png

Figure 8: Source: SAP

 

Figure 8 shows Geo enhancements for SAP BusinessObjects Web Intelligence

9chart.png

Figure 9: Source: SAP

 

Figure 9 shows chart improvements and the server dependency.

10filters.png

Figure 10: Source: SAP

 

Offline table filter is similar to Excel, table with 100 rows and apply filter on columns

11persviewenh.png

Figure 11: Source: SAP

 

Starting this release support personal views with Prompts

 

Also supports sections with personal views

12persvieinput.png

Figure 12: Source: SAP

 

Show meaningful filter values

 

Only see filter values selected in the prompt window

 

Hierarchical input controls supported

13alias.png

Figure 13: Source: SAP

 

Alias is easier for you to remember

 

Table actions performed and can be retained - sort

 

14alerts.png

Figure 14: Source: SAP

 

Figure 14 shows updates for personal views; can access offline

15webiperf.png

Figure 15: Source: SAP

 

Complex server operations now avoided; being more efficient

 

Users do not need edit rights to mobilize documents

 

Note server dependency

16lumira.png

Figure 16: Source: SAP

 

For Lumira, they have enabled caching – subsequent access will be faster

 

Available in apps store – download to today and test new features

 

SDK version is available

 

Documentation is live too

 

Android

17ui.png

Figure 17: Source: SAP

 

Android is up to speed of iOS

 

More features are seen on the Android.

 

Favorite document is now available in Android

18newcat.png

Figure 18: Source: SAP

 

Category management was not available on Android device – assign documents to categories

 

Also includes BI Inbox Support

 

SSO support for Androids as well

 

SSO Kerberos for Android is not supported yet

25DESIGNSTUDIOONANDROID.png

Figure 19: Source: SAP

 

Figure 19 shows support for SAP BusinessObjects Design Studio on the Android.

 

Other Android Features coming:

 

  • Personal views from Web Intelligence now supported on Android
  • Catchup features include Micro Bar Chart supported on Web Intelligence – follow special syntax
  • Geo enhancements POI for Android


Android will be available in 1 week

SDK in SMP in 1 week

 

26biplatformdep.png

Figure 20: Source: SAP

 

Figure 20 shows the server prerequisites.

 

Question and Answer

Q: Is there any plans to allow opendocument documents to saved to personal views?

A: Opendoc links can be accessed for offline - not saved to personal views - something to consider for future.‑

________________________________________________________________

Q: is the new version of Mobile 6.0 is BOE platform dependent - meaning does it work on BOE 4.1 SP2 or only works after 4.1 SP03 onwards...?

A: See slide for prerequisites‑

________________________________________________________________

Q: are these saved prompts on the client or on the BO servers?

A: Saved prompts are on the client.‑

________________________________________________________________

 

Q: For security reason, we had to disable the Document download icon. Since then, we are unable to assign Favorites and Categories. When will the Document download "unlink" from Favorites/Categories?

A: Working on this feature for H2 release‑

________________________________________________________________

 

Q: do you have any plan to support PDF files exposed thru mobile devices. e.g. if you create a hyperlink in BOE to read a PDF document and assign it to mobile category. From mobile, click on the report icon, and open the PDF file inside of the mobile app.

A: This works as of today. ‑

________________________________________________________________

Q: What is the roadmap for a Win 8.1 version?

A: Closely monitoring the market for Windows 8‑

________________________________________________________________

Q: any plan to make it work inside of mobile

A: PDF works within Mobile; if want to access agnostic documents - currently not possible but considering going forward‑

________________________________________________________________

Q: Availability date  of Mobi 6 SDK ?

A: Available today for iOS‑

________________________________________________________________

 

Also see Power of ASUG Influence : How ASUG members Influenced SAP BusinessObjects Mobile BI Solution

Late today I saw on twitter that the latest release of BusinessObjects Mobile 6.0.3 iOS was released.  So what is new?  It is listed on iTunes at SAP BusinessObjects Mobile on the App Store on iTunes

 

What's New in Version 6.0.3

• Support for SAP Mobile Platform 3.0

• Support for SAP Mobile Platform, cloud edition

• User experience improvements

• MDM configuration support for iOS 7 devices

• Support for local table filtering for SAP BusinessObjects Web Intelligence documents

• Personal views, geo analysis, and performance enhancements for SAP BusinessObjects Web Intelligence documents

• Technical enhancements

 

Source: iTunes/SAP

 

Looking at the user experience improvements, I noticed the following:

 

fig1.PNG

 

Figure 1

 

Figure 1 shows adding to favorites is available as a separate action.

2fig.PNG

Figure 2

 

Figure 2 shows new icons for what can be downloaded to the device and what cannot.  I also selected eFashion document as a "favorite".

3fig.PNG

Figure 3

 

The next time I log on to Mobile BI, it takes me straight to "Favorites" instead of "All Reports" as shown in Figure 3.

4figwifi.PNG

Figure 4

 

Figure 4 shows a new feature to automatically update documents when connected to wi-fi.

5fig.PNG

Figure 5

 

Figure 5 shows the Work Offline button is now available in the Connections listing on the left panel.

 

On twitter, I was told this:

I haven't downloaded the ESRI trial and I am not a big user of Web Intelligence, but I may try.

 

The SAP Help has not been updated yet but when it is it will be at SAP BusinessObjects Mobile for iOS – SAP Help Portal Page

 

I am sure we'll hear more details next week on this ASUG webcast:

Actions

Filter Blog

By author:
By date:
By tag: