Neudesic Blogs

Summary

Adding properties to the profile page on a user's My Site is done through the Shared Services Administration site. The following is a walkthrough on how to add the Department property to the profile page for each user.

1. Open Central Administration and click the Shared Service provider that hosts the My Sites
2. Click User profiles and properties

1. Click View profile properties

1. Locate the property you wish to have displayed and click Edit

1. Select the checkbox next to Show in the profile properties section of the user's profile page

1. Click OK

Note:

If the property does not appear on the Profile page the value may be empty for the active user.

To use a custom master page with view.aspx or taskview.aspx perform the following:

1. Copy the desired master page into the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\NCF directory.
2. Update the master page to include the following line after <SharePoint:Theme runat="server"/>
   1. <link rel="stylesheet" type="text/css" href="/_layouts/ncf/styles/ncf.css"/>    
3. If you master page does not contain a Form digest ensure the following is included

   <asp:ContentPlaceHolder id="PlaceHolderFormDigest" runat="server">

        <SharePoint:FormDigest runat=server/>

   </asp:ContentPlaceHolder>

    

4. Navigation to the Canvas Configuration list and locate the MasterPage key. Note: You can specify a custom master page for all Views, a specific View Instance, or a specific View/View Instance. To change the setting globally, change the item that is of type NCF Configuration
5. Edit the MasterPage key to specify the new master page

Example

HOW To: Change a Narrative Template

ACES provides the ability to create Microsoft Office Word 2003 documents that are integrated with the ACES Control Environment. By default, the document contains generic header and footer information that you may want to customize. The "How To" outline the process for customizing, what is commonly referred to as, a narrative template.

Figure 1: Unprotect Dialog

Locating the Narrative Template

By default, all narrative templates are located in the directory, C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\SOX\TEMPLATES.

Note: To perform this operation you must have Microsoft Office Word 2003. If the server does not have Word installed you will need to create a copy of the process.doc to a machine with Word 2003 installed

Unprotect Process.doc

1. Located the document process.doc
2. Create a backup copy of the file called process.org
3. If you are using Word on a machine other than the server, create a local copy of process.doc.
4. Right-click on the process.doc you are working with and select Edit
5. Once Word open, click Tool…Unprotect Document
6. When prompted for a password, type in Secure. ACES uses this password simply to prevent the user from accidentally changing a file. It does not provide any true security and changing this in not supported.
7. Click OK
8. Process.doc is not unprotected and you are free to make changes. Once you have made the required changes you will need to perform the steps in the section Protect Document.

Note: You must perform the steps in Protect Document to ensure proper functionality

Important: The XML tag of Narrative must be a part of the document or editing narratives will not work. Removing the Narrative tag is unsupported

Protect Document

After you have made the required changes to the process.doc file, you will need to use the Protect Document feature of Microsoft Office Word 2003 to ensure proper functionality. The following is a step-by-step process for protecting process.doc

1. From Microsoft Office Word 2003, select the region of editable text between the 2 Narrative tags. See screenshot below. Note, if you have ACES Narrative Composer installed you will receive a error that states Value cannot be null. This is expected and you can ignore the error. For more information refer to the article Editing XML Data with Microsoft Office Word 2003 and Microsoft Office Excel 2003 at http://msdn.microsoft.com/en-us/library/aa159889(office.11).aspx

Figure 2: Selecting the editable region of process.doc

1. Click Tools…Protect Document
2. Click Yes, Start Enforcing Protection
3. In the Start Enforcing Protection dialog, you must enter the password of Secure in the Enter new password and Reenter password to confirm
4. Click OK
5. Click File…Save

Figure 3: Start Enforcing Protection

Additional Steps

If you created a local copy of process.doc you will need to copy it to each Front End Server.

1. Copy process.doc to the directory C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\SOX\TEMPLATES
2. Repeat step 1 on each Web Front End

In certain situations security changes made in CSAT will not be reflected and users will appear to have no access to nodes within the Control Environment. If this occurs do the following ensure the ACES Add Copy, ACES Read Only, ACES Assign and ACES Read Edit Permission Levels include the Enumerate Permissions site permission

Office Canvas Version 1 will include a new capability for generating SQL statements that can be used for advanced reporting on SharePoint data. These statements include SELECT, SELECTINTO, and CREATEVIEW. Using the function fn_ncf_BuildListSql will return a SQL statement can be executed against a SharePoint Content Database to return list data. The following are usage examples:

SELECT INTO

declare @s varchar(max)

exec @s = fn_ncf_BuildListSql 'SELECTINTO', '', 'Canvas Tasks', '##MyTempTable', ''

exec(@s)

SELECT

declare @s varchar(max)

exec @s = fn_ncf_BuildListSql 'SELECT', '', 'Canvas Tasks', '', ''

exec(@s)

CREATE VIEW

declare @s varchar(max)

exec @s = fn_ncf_BuildListSql 'CREATEVIEW', '', 'Canvas Tasks', '', 'CanvasTasks'

exec(@s)

The following error can occur if the location of SoxItemsUIAssembly.dll is incorrectly referenced in the metadata that was imported. To resolve this issue do the following

1. Open the IBF Meta data file that was imported
2. Search for the following line <Port xsi:type="PortAssembly" Name="Asm.UI.SoxItemsUIAssembly"
3. In the Location attribute of that line, ensure the value points to the actual location of the SoxItemsUIAssembly.dll" For example, C:\Program Files\AVIVA Consulting Group\Narrative Composer\2.1\bin
4. Import the updated Metadata using the IBF Settings Manager

Error Message:

The specified assembly failed to load the Aviva.Aces.Narratives.SoxItemsTree control.

Stack Trace:

Microsoft.InformationBridge.Framework.Interfaces.UIException: The specified assembly failed to load the Aviva.Aces.Narratives.SoxItemsTree control. ---> Microsoft.InformationBridge.Framework.ExecutionEngine.EngineException: MetadataScope[Aviva.Solutions.IBF.Narrative].Port[IBFNarrativeSolution:Asm.UI.SoxItemsUIAssembly]: Cannot load specified assembly. ---> System.IO.FileNotFoundException: File or assembly name SoxItemsUIAssembly.dll, or one of its dependencies, was not found.

File name: "SoxItemsUIAssembly.dll"

at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Boolean isStringized, Evidence assemblySecurity, Boolean throwOnFileNotFound, Assembly locationHint, StackCrawlMark& stackMark)

at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Boolean stringized, Evidence assemblySecurity, StackCrawlMark& stackMark)

at System.Reflection.Assembly.Load(AssemblyName assemblyRef, Evidence assemblySecurity)

at Microsoft.InformationBridge.Framework.ExecutionEngine.Utility.LoadAssembly(AssemblyName assemblyName)

at Microsoft.InformationBridge.Framework.ExecutionEngine.AssemblyPort.get_Assembly()

=== Pre-bind state information ===

LOG: Where-ref bind. Location = C:\Aviva Solutions\src\narrative composer\Version 1.0.0.1\IBFNarrative_ControlLib\bin\Debug\SoxItemsUIAssembly.dll

LOG: Appbase = C:\Program Files\Microsoft Information Bridge\1.5\Framework\

LOG: Initial PrivatePath = NULL

Calling assembly : (Unknown).

===

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

LOG: Attempting download of new URL file:///C:/Aviva Solutions/src/narrative composer/Version 1.0.0.1/IBFNarrative_ControlLib/bin/Debug/SoxItemsUIAssembly.dll.

--- End of inner exception stack trace ---

at Microsoft.InformationBridge.Framework.ExecutionEngine.AssemblyPort.get_Assembly()

at Microsoft.InformationBridge.Framework.ExecutionEngine.CustomOperation.get_Assembly()

at Microsoft.InformationBridge.Framework.UI.GlobalHelpers.TryCreateInstanceFromPort(String typeName, IPort port, IMediator mediator, String targetInstance, Boolean fullTrustCheck, Boolean& errorHandled)

--- End of inner exception stack trace ---

Software Installation

• Uninstall previous version of ACES
• From a command prompt in the c:\program files\Neudesic\Aces\Server\SharePoint directory execute the following
  • Stsadm –o upgradesolution –name Neudesic.Aces.wsp –filename Neudesic.Aces.wsp –local –allowGacDeployment
• From a command prompt in the c:\program files\Neudesic\Aces\Server\bin directory execute the following
  • Soxreg –o setinstalldir –dir "C:\Program Files\Neudesic\ACES\Server

Post Install Steps

• Run the ACES Configuration Manager
  • Click All Programs…Neudesic…Aces…ACES Server Configuration Manager
  • Click Reporting
  • Specify values for SQL Reporting Services integration
  • Click Apply

  

Configuring Automated Report Export

• Open c:\windows\system32\jobs.xml in notepad
• Add the following line to the Jobs element. This will run every 10 minutes

    <Job interval="600000" filename="C:\Program Files\Neudesic\ACES\Server\bin\soxjobs.exe" arguments="-o reports" nowindow="false" useshell="false" useserviceaccount="true"/>

Executing the following SQL: Aces_PostImportProcess System.Data.SqlClient.SqlException: Invalid object name 'Aces.dbo.SharedReference'.

This error occurs when the default database name of 'ACES ' is not used for the caching database. To resolve this error edit the stored procedure [Aces_ImportSharedReferences]. Change the line

select SoxDocuments.DocumentId, sd2.DocumentId as ParentId from

    Aces.dbo.SharedReference sr1

to reference the correct database. For example, if your Aces caching database is set to ACES_CACHE then update the line to read

select SoxDocuments.DocumentId, sd2.DocumentId as ParentId from

    ACES_CACHE.dbo.SharedReference sr1