Transitioning from PC Scribe to Web Scribe

• A new version was released with 4.1.5
• You will transition when you are ready
• You should move soon; PC scribe is packing its bags
• All of this information is in the admin guide

• Understanding the new database table
• Copying blocks to new table
• New UCX-CFG020 glag
• Scribe reports
• Running dap16
• Running audits
• Moving from TEST to PRODUCTION

• New database table - dap_req_BLOCK
• test in CLOB
• Old was 
• dap_req_MST
• dap_req_TEST_dtl
• PC Scribe reads/saves changes to the dap_req_mst table
• Web Scribe reads/saves to the new dap_req_block table

• Copying blocks to new table
• The req-MST and req-TEST-dtl data is only copied.  it is not deleted
• dapreqs2reqblock <- script to copy blocks from old to new
• Now blocks will be available in Web Scribe
• run once when you are familairiazing yourself with web scribe
• run again when you convert

• UCX-CFG020 DAP14 Use RapReqBlock flag
• While playing around, keep this 'N'
• saving in web scribe will not affect audits
• saving in PC scribe will like usual
• Setting to 'Y', the opposite will happen
• A friendly reminder occurs when you save in the opposite software of the setting of the flag
• dwenv.config -> modify to add the email addresses (dap16, dap22, etc)
• Scribe Reports - run in Transit
• SCRnn reports also obey the CFG020 DAP14 UseDapReqBlock flag
• Run SCR06 after changing the CFG020 flag
• Once flag is changed all reports use the new table
• but yes, you can change the flag back to N
• ODS - need to install the patch since data needs to come from the new table
• Update any of your reports
• running DAP16
• daptrees directory -> compiled version of the block -> used by the auditor
• DAP16 obeys the flag
• So, use DAP16 to recompile the blocks
• If you change the flag back to N, run dap16 again
• Exceptions are still valid; you will not use them
• Tied to a block number, it doesn't change
• Running audits
• GetBlocks - find the right blocks for this student's curriculum
• A database view mimics the layout of the req-mst
• dap_req_block_vw
• While testing web scribe keep flag to N
• Moving from TEST to PRODUCTION
• Assuming your gold copy of blocks is in TEST
• While testing web scribe keep flag to N
• Switch flag to Y and do previous steps in TEST
• Make changes to next catalog in TEST
• In production set flag to Y in PROD
• If you have RB planner blocks then convert all blocks to new Scribe table using dapreqs2reqblock in PROD (just do this anyway)
• In TEST, unload just the RA blocks: dapblockunload RA testenv.tar
• copy the tar file from admin/datac in TEST to datac in PROD
• in PROD, load the blocks: dapblockload RA testenv.tar
• in PROD, run DAP16 to reparse vlocks in dap_req_BLOCK
• run webrestart and daprestart
• Done